ID | Team Blocked | Blocked by | Team that needs to Respond | Notes | M2 Blocking Y/N | Resolved Y/N |
---|---|---|---|---|---|---|
B1 | VoLTE usecase/ Integration/CLAMP/Holmes | Identify the story of fault correlation and auto-healing. | VFC | Which VNF, what kind of fault, etc. Needed for M2 integration test case design -by 7/30 Feedback from CMCC: is talking with vendor to check the capabilities of VNF event generation. Should provide answer by 8/3 | Y | N |
B2 | VF-C | VES Collector API,nfc/nfnaming standard | DCAE | DCAE R1 Release Planning#APIOutgoingDependencies Feedback form Yan, need more details about the API,the parameter in the URI is undefined. | N | |
B3 | Holmes | Code: message get from and back to DMaaP | DCAE | Need the sample to learn how to get message from and back to DMaaP. | N | |
B4 | Holmes | APIs for service registration and discovery, etc. | DCAE | How to register services to the Consul? How to get the address or endpoint of other services via Consul? Where and how to pull the rules designed during the run time? Feedback from Lusheng, the high level API will be provided by M2, and the full API spec. by M3. | N | |
B5 | Holmes and VF-C | DMaaP API: sub/pub, query, etc. | DmaaP | Pamela Dragosh: If Ramprasad Koya or Varun Gudisena could provide a wiki page or documentation for this API that would be great. Both the Holmes and VFC team need to know the work involved in integrating this. Feedback from Varun, the API documentation for DMaap will be availabe by August 3rd. | N | |
B6 | Policy | VF-C API invoked by Policy | VF-C | Pamela Dragosh: The policy team requests that VF-C use the Dmaap API that is identical to what APPC supports today. Having a common Controller API would be ideal. Feedback from Yan, VF-C are working on the rest API that provide to policy,the rest API plan to be available by August 3rd.While VF-C team are analyzing the Dmaap API to decide whether to use DMaap or not in R1 | N | |
B7 | Holmes | Holmes component spec., DMaaP topic + message, rules, etc. | Holmes | To work with the control loop, Holmes needt o do a lot of work. Guangrong Fu: the component-spec file has been sent to the DCAE team. Waiting for the response. Guangrong Fu: A sample rule could be found at Holmes Weekly Meeting (20170720) | N | |
B8 | vCPEuse case/Integration | To confirm the interface between SDC and CLAMP | SDC/CLAMP/DCAE | SDC, CLAMP, DCAE have confirmed that the interfaces among them for closed loop control have been defined, implemented, and tested. | Y | |
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. | 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. | N | |
B12 | SDC | The work flow repo | SDC | During the virtual developer meeting, Michael response that he will take care of it. | N | |
B13 | Holmes | Holmes is not able to call A&AI RESTful APIs while integrated with DCAE. | MSB/OOM/DCAE | Need DCAE to be integrated with MSB for service discovery. | N | |
B14 | VoLTE usecase/ Integration/SO/VFC | SDC VoLTE use case support | SDC | Identify the gaps before the functional freeze milestone, here are the action items and date.
| Y | N |
B15 | SDC/VFC integration | VoLTE usecase support | SDC | Identify the gaps before the functional freeze milestone, here are the action items and date.
| Y | N |
B16 | VNF SDK | Need to understand process for handing-off TOSCA packaged VNFs for onboarding | SDC | Need to understand how we can transfer VNFs from the vnfsdk package validation tool to SDC once the VNFs have been validated | N | Y |
B17 | VF-C | VoLTE usecase related instances persistence Need to confirm if adding new attributes will impact other projects | A&AI | James Forsyth will provide instructions for adding new attributes that used in VoLTE usecase in A&AI scheme. Complete - see this page: Tutorial: Making and Testing a Schema Change in A&AI | ||
B18 | SO | VFC NBI definition for SO | VFC | Need VFC NBI definition -by 7/31 Feedback from Yan, VF-C team have discussed the interface with so team and will provide the interface document by 7/31 | 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 | N | ||
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 | N |