| ID | JIRA / helpdesk # (if applicable) | Team Blocked | Blocked by | Team that needs to Respond | Notes | M2 Blocking Y/N | M3 Blocking Y/N | Plan for closure (provide the plan and expected closure date) | Resolved Y/N | B4 | Holmes | APIs for service query (like the info of services which are registered to the DCAE Consul) and configuration loading, etc. | DCAE | How to get the external IP of the services via Consul? Where and how to pull the rules designed during the run time? When will the detailed APIs be provided? Feedback from Lusheng, the high level API will be provided by M2, and the full API spec. by M3. 8/21 - Vijay Kumar: Holmes when deployed by DCAEGEN2 will be registered into Consul by the platform. Run-time rules will be pushed into container as updated configuration (K-V pair) | N | N |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| B9 | vCPE use case/Integration | To confirm the vCPE service model are fully supported by SDC. | SDC | The vCPE team has called a meeting on 7/27 to address this. Michael Lando: vCPE is supported, sdc team is waiting for the vnf files to be able to validate them and test there onboarding. | N | |||||||||||
| B10 | VoLTE usecase/Integration | Confirm if SDC can import TOSCA template and view/edit the template | SDC | Feedback: The answer got during July virtual developer event was SDC supports TOSCA, but need to check if VoLTE template from Open-O (that's what VFC is expecting) can be supported. | N | |||||||||||
| B11 | MSB | A repo under OOM to accommodate the registrator codes which integrate OOM and MSB | OOM | Request has been sent out to OOM PTL but no response yet. | Y | |||||||||||
| B12 | SDC | The work flow repo | SDC | During the virtual developer meeting, Michael response that he will take care of it. Michael Lando: the repository was created sdc is waiting on confirmation on the committer creation for the project. | N | |||||||||||
| B15 | SDC/VFC integration | VoLTE usecase support | SDC |
| N The material from VFC has provided. The VFC team needs the SDC team feed back and get the NSD and NS package, VNF package output from SDC, which is part of the API definition. | |||||||||||
| B19 | SO | Clearly define and document SDC output and its content, including recipe, model, and other artifacts | SDC | N | N | N This is an issue not a blocker. | ||||||||||
| Y | ||||||||||||||||
| Y | ||||||||||||||||
| Y | ||||||||||||||||
| N | N | Received Carbon ODL Docker from CCSDK; working to integrate into APPC now. | Y | |||||||||||||
| B24 | SO/APPC/VID/Policy/AAI/SDC/SDNC/DCAE/PORTAL | ONAP R1 at risk, if the decision is to migrate to *.onap.org | TSC | This topic has been raised to onap-tsc mailing list and will be discussed with ONAP TSC on Thursday 8/3 https://lists.onap.org/pipermail/onap-tsc/2017-August/001436.html | N | N | ||||||||||
| 8/23 - OOM will be deploying dmaap; no longer blocker for DCAE | N | |||||||||||||||
| B26 | DCAE | Need to understand how API endpoints provided by other ONAP components are configured/communicated to when ONAP is deployed. For example, how would DCAE know where is the A&AI API. Is this well-know via a DNS C-name or via service discovery. If the latter, how. | Integration or OOM | Pending decision from Integration team meeting planned for 8/28
| N Results from 8/7 meeting: when ONAP is deployed by HEAT, the service discovery is clear. When ONAP is deployed by OOM, it needs more discussion. In another meeting which OOM/DCAE/MSB/Integration teams participated, no conclusion could be made on how MSB integrated with OOM. | |||||||||||
| B27 | DCAE | Need to understand how the whole ONAP system is brought up, and how various per-deployment configuration parameters are communicated to individual ONAP components and subcomponents. | Integration or OOM | Pending decision from Integration team meeting planned for 8/28
| N Results from 8/7 meeting: when ONAP is deployed by HEAT, the mechanism of parameter passing is clear. When ONAP is deployed by OOM, it needs more discussion. | |||||||||||
| B29 | CLAMP | Interface content change | Policy, DCAE, SDC | 3 potential changes might affect CLAMP development :
| N | N | CLAMP team will account for these changes in next sprints but the sooner the change is identified the better. | N | ||||||||
| B30 | DCAE | Availability of a Pypi server on LF Nexus | Linux Foundation | DCAE needs a Pypi server for hosting Python packages built from ONAP DCAEGEN2 Python code so they can be installed at runtime. Email requests sent to onap-helpdesk@rt.linuxfoundation.org <onap-helpdesk@rt.linuxfoundation.org> but received no ticker number. | ||||||||||||
| B31 | OOM | Availability of stable code / docker image for:
| SO DCAE | OOM needs to have stable and working docker images in order to complete deployment specs. | ||||||||||||
| B32 | VNFRQTS | Jenkins / Verify | LF + documentation manages the jenkins task for all documentation | Difficult for the VNFRQTS project to progress unless we can have visibility of our work product at onap.readthedocs.io | Y | Y | working with LF + Docs to resolve | N | ||||||||
| B33 | DCAE/Holmes/POLICY | Clarification on A&AI API calls during Control Loop runtime by the various components. | A&AI | Pamela Dragosh will provide more details for this blocking issue. | N | N | M4 Blocking Pamela Dragosh will create a wiki to clarify the outstanding issues. Schedule subsequent meeting with the teams to resolve. | N |
...
ID | JIRA / helpdesk # (if applicable) | Team Blocked | Blocked by | Team that needs to Respond | Notes | M2 Blocking | Resolved Y/N | ||
|---|---|---|---|---|---|---|---|---|---|
| Y | Y | |||||||
| Y | ||||||||
Y The test script for interfacing with DMaaP Message Router can be found at "git clone http://gerrit.onap.org/r/dcae/demo/startup/message-router", then look into docker_files/tests/test.sh. | |||||||||
| Y API Documentation is available at | ||||||||
| Y | ||||||||
| |||||||||
| |||||||||
| |||||||||
| Y | Y | |||||||
|
| Y | |||||||
| Y | ||||||||
| |||||||||
| |||||||||