Template:
- What has your team achieved in past one week?
- Block issues / help needed from the community
- Testing
- Commited python parent POM for ONAP.
- Added the vcpe heat templates for the first use case
- Working to do the distribution stuff in asdc hopefully this week
- Reference VNFs
- Nothing new to report on this project at this time
- 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
- 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.
- Release / O-Parent
- Independent Versioning and Release Process officially rolled out to the community
- JIRA tickets logged against all project for tracking
- A checklist item has been added to M4 and RCx checklist template
- ONAP Version Manifest Maven Plugin for checking dependency versions has been rolled out
- O-Parent has released two versions of artifacts so far; current version is 0.1.1
- Initial version of O-Parent for Python has been added
- Ongoing help to the community on Jenkins jobs, CSIT, O-Parent implementation
- Independent Versioning and Release Process officially rolled out to the community