...

• 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:
    • ActionCancelActionCancel  (will not be part of Beijing Release)
    • ActionStatus
    • AttachVolume
    • DetachVolume
• 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

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

The use cases supported in Amsterdam release will continue to be supported as part of regression assuming all other components do likewise.

At this writing, APPC will not be contributing to any APPC contribute to two use cases as part of the functional requirements.

• Manual Config Scale Out will be supported..

...

• Change Management did not flag APPC has impacted because the use case they are looking at is focusing on an L3 VNF, so that would be the pervue of SDNC to do the in place software upgrade; however, if it was an L4-L7 type VNF, this would be APPC executing action. APPC will be adding capability to support an in-place software upgrade

...

• . We will contribute the code, but don't have a specific use case planned to exercise it. 
•  

Minimum Viable Product

Describe the MVP for this release.

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

• CCSDK - - Nitrogen ODL & MariaDB
• AAF - feature AAF-91 - needed to address API level security
• SO - for manual scale out scenario

Architecture

High level architecture diagram

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...