...

• Remove references and use of openecomp and replace  with onap 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 new use cases .

The Change Management use case is working with SDNC for an L3 device firmware upgrade; however, note that APPC will be adding capability to do an in-place software upgrade for a VNF)

Discussions are still taking place around the manual Scaling use case; however, no definitive outcome at this stage due to lack of resources.

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.

...

The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make no assumptions about the network. Support configuration and lifecyle management of VNF/VNFC in a generic fashion so that on-boarding any new VNF/VNFC is just a matter of configuration and data. Longer term items include:

• Automated scaling
• Support beyond Openstack and move to an adaptor type architecture so that multiple types of clouds can be supported with little effortSupport different types of clouds, currently only support Openstack; Looking at re-architecting the southbound IaaS adapter to allow plugins for different cloud abstraction solutions  (CDP-PAL, MultiCloud, etc...)
• Align to the controller architecture proposed as part of ONAP by the architecture team.

...

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

...

For the Beijing release, APPC has dependencies on the following three projects for specific deliverables:

• CCSDK - - Nitrogen ODL dockerSDNC -  & MariaDB docker
• 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.

...

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

• Unit CSIT tests are run automatically added as part of every code merge.
• Once the final Docker image is compiled, it will be installed onto a Docker host and will be checked to ensure no errors occur during start-up.
• Functional testing will occur to ensure that the use cases are functioning correctlyR1 will continue to be supported in R2
• Pairwise testing will be done in the WindRiver Dev lab similar to what was done in R1.
• Epics are created to track testing activities to address Platform Maturity items.

• Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

...

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...

• Documentation, Training

• Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
• Highlight the team contributions to the overall Release Documentation and training asset
• High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
• Documentation includes items such as:
  • Installation instructions
  • Configuration instructions
  • Developer guide
  • End User guide
  • Admin guide
  • ...

Documentation updates planned for Beijing release are tracked under Documentation Epic: APPC-308

Other Information

• Vendor Neutral

...