...
- Remove references and use of openecomp and replace with onap
- Address Platform Maturity requirements to the extent possible to comply with minimum requirements requested for Beijing. Further details below in Platform Maturity table.
- Support AAF (Authentication and Authorization Framework) for API access
- Dependency on AAF project to provide feature (AAF-91) to enable AAF security on the web server level (jetty level). AAF has accepted the story for Beijing.
- Upgrade ODL version to Nitrogen (driven by CCSDK dependency)
- Replace MySQL with MariaDB (driven by CCSDK/SDNC dependency)
- Increase Code Coverage to 50%
- Provide support for the following new LCM actions:
- Following Actions in support of In-place software upgrade
- QuiesceTraffic
- ResumeTraffic
- UpgradeSoftware
- UpgradePreCheck
- UpgradePostCheck
- UpgradeBackup
- UpgradeBackout
- Additional LCM actions including:
ActionCancel(will not be part of Beijing Release)- ActionStatus
- AttachVolume
- DetachVolume
- Following Actions in support of In-place software upgrade
- Contribute CDT Tool - an APP-C Design Tool enabling VNF owners to create templates and other artifacts used by APP-C Configure actions (used to apply a post-instantiation configuration) as well as other life cycle commands.
- Documentation updates for Beijing
- Support new LCM action for ConfigScaleOut
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
ODL upgrade to Nitrogen & DB to MariaDB - depends on CCSDK/SDNC projects | Accept risk | None |
| AAF delivery of AAF-91 in time to allow APPC to complete and test their work | Working closely with AAF team to understand their design approach | Turn AAF off for Beijing (same as in Amsterdam) |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...