...
- 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 (Decommissioned) 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
E2E Integration Lab
- The ONAP deployment environment is being deployed, plan to install WindRiver Titanium to keep align with Developer lab.
- VNF vendors, Huawei and ZTE, are deploying VNFs in TIC Edge to integrate with VIO 4.0, will be done by the end of this week.
- Nokia is deploying vISCSCF and vTAS in TIC core, the task is almost be done, there is some issues should be handled in this week
- We will begin to integrate VNFs from different vendors together next week, do some service level configuration manually to try to make a successful VoLTE call.
- Developer Lab
- Had a meeting to scrub the bugs reported lately by integration team, and listed out top blocking issues.
- Tested ONAP1.1 branch. Created 6 new JIRA tickets
...