| 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 Venkatesh 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 | Identify the gaps before the functional freeze milestone, here are the action items and date.
| N | ||||
|
| ||||||||
| B19 | SO | Clearly define and document SDC output and its content, including recipe, model, and other artifacts | SDC | N | |||||
| B20 | Multi VIM/Cloud | ARIA flow interfaces for Multi VIM | SO | Need to identify basic scope for R1 and function test case | N | ||||
| B21 | Multi VIM/Cloud | APP-C interfaces for Multi VIM, Should we support VM status get, stop, start for R1 use cases? | APP-C | Need to identify API for R1 and function test case for VCPE use case | N | ||||
| B22 | Multi VIM/Cloud | scope for R1 | DCAE | identify DCAE service delopyment interfaces for Multi VIM, interfaces called by Cloudify | N | ||||
| B23 | APPC | Dependency on SDNC for ODL Docker | SDNC | APPC is dependent on SDNC for the ODL and must align on same version. SDNC is planning to upgrade to Carbon, so APPC must also upgrade. ETA for Carbon Docker was end of July, but reforecast to 8/4. ODL upgrade has been problematic in the past, so important to get this as soon as possible to start integration. | N | N | |||
| 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 | |||
| B25 | DCAE | Need DMaaP deployment blueprint for ONAP R1 | DMaaP | 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 | Feedback: have scheduled a meeting on 8/7 to discuss the issue. | 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 | Feedback: have scheduled a meeting on 8/7 to discuss the issue | 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. | |||
| 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. |
...