...
- vCPE Use Case
- The vCPE team had a meeting with SDC and MSO teams the past week. As a result, MSO team suggests to change the current Heat templates in order to clearly separate Networks and VNFs.
- This separation represents a more realistic scenario, in which a VNF service (designed via SDC) uses a pre-existing network service from the catalog.
- Teams are discussing what MSO and SDN-C APIs to use, without adding new code at this stage of the project
- Reviewed VPP-based VNF development. The work is finishing up. A minor problem will be fixed soon, and the doc will be released this week.
- Communicated with DCAE to find that both the collector and analytics app have base code ready. Optimization work is ongoing.
- Reviewed workflow design and test with SO team. SO just updated the repo to v1.1, which is a major code merger. SO team did state that the workflow design and test is non-trivial. The team will have another session on this to understand if there is blocking issues and what could be the solution.
- The team has started M4 progress checking for each design and test item: vCPE Design and Test Cases
- ONAP installation for Amsterdam release (OOM vs. Heat)
- Added a new CLAMP VM to the Heat stack, as per CLAMP team request.
- Installed ONAP via OOM multiple times in the WindRiver lab. There are issues due to resource limitation (the current VM cannot host more than one full ONAP instance)
- Health status of the ONAP platform doesn't seem dependent on the installation method.
...