| 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 |
|---|---|---|---|---|---|---|---|---|---|
| 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: the vnfs for vcpe were successfully onboarded and distributed . there is no issue from the SDC side. | Y | ||||
| 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. is avilable and the work flow code is there already | Y | ||||
| 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 | Michael Lando sdc has documented all the external api and destribution info. please remove thsi blocker or spcify what exactly is needed. | 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. | |||||
...