...
- 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 BeijinglBeijing. 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
ActionCancel(will not be part of Beijing Release) - ActionStatus
- AttachVolume
- DetachVolume
- ActionCancel
- 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
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 in Beijing.
...
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.
There is no impact for APPC as part of HPA use case at this point.
Discussions are still taking place around the Scaling use case; however, no definitive outcome at this stage.
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. Additional long term goal is to align to and data. Longer term items include:
- Support 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.
...
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description | Deliverable Location |
---|---|---|
"App-c Image" Docker Container | Executable | Docker images available on nexus3 |
Java Source Code | The Java code for the main App-c components. | appc Git repository |
Deployment Scripts | Linux shell scripts and Maven pom files used to generate the Docker containers. | appc/deployment Git repository |
Directed Graph Xml Files (DGs) | Xml files define the directed graphs which are installed to database during startup and are used to determine actions taken by app-c | appc/deployment Git repository |
Yang Model Files | Yang files are used to define the... | appc Git repository |
Property Files | Property files are used to define values that may need to be changed depending on the environment app-c is run in.depending on the environment app-c is run in. | appc Git repository |
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 | appc/cdt Git repository (NEW) appc Git repository |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall 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.
ONAP Dependencies
...
Dependencies
List the other ONAP projects you depend on.
APPC interacts and has dependencies depends on the the following components as part of the general ONAP architectarchitecture:
- SDC: Rest based interface exposed by SDC. APPC receives notifications from SDC on VNF information. SDC team provides an SDC Listener, which is used by APPC.
- AAI: APPC retrieves and updates VNF data from/to AAI.
- DMaaP: Message bus for communication with other components in the solution (SDC, DCAE, MSO, Portal, OOM)
- CCSDK - APPC currently gets ODL & DB package from CCSDK; CCSDK and APPC currently must align on ODL version.
- AAF - AAF is used for authentication of APIs
- MultiVIM - APPC can access Openstack via MultiVIM or CPD-PAL. MultiVIM is optional for APPC at this stage.
For the Beijing release, APPC has dependencies on the following two projects to deliver updated componentsthree projects for specific deliverables:
- CCSDK/SDNC - - Nitrogen ODL and & MariaDB dockers
- AAF - feature AAF-91 - needed to address API level securityaddress API level security
- SO - for manual scale out scenario
Architecture
High level architecture diagram
...
Anyone reading this section should have a good understanding of all the interacting modules.
For details on the APPC architecture, refer to the APPC User Guide.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
---|---|---|---|---|
Performance | 0 | TBD0 | Awaiting guidance from Benchmark subcommittee |
|
Stability | 0 | 1 | APPC will do a 72 hr soak test We assume integration team will do a 72 hour soak test at the platform level. |
|
Resiliency | 1 | 12 | Clarification was provided by Jason Hunt that Level 1 is manual failure detection and recovery within a single site. APPC leverages CCSDK/SDNC distributions of OpenDaylight and DB. We will work closely with CCSDK/SDNC team to leverage what they are doing and not duplicate effort. CCSDK indicates Level 2 support, so Level 2 will be a stretch goal for APPC at this stage until we have a better understanding of dependency. |
|
Security | 0 | 1 | We will target 50% Sonar coverage for Beijing and completing complete the Passing badge Survey. |
|
Scalability | 1 | 1 | APPC uses ODL distribution from CCSDK project. Scaling is a function of ODL capabilities - adding nodes to an existing cluster or adding a new cluster. APPC can be scaled either by adding additional OpenDaylight containers and/or database containers, or by deploying multiple instances of APPC cluster. |
|
Manageability | 1 | 1 | APPC supports/integrates EELF. |
|
Usability | 1 | 1 | Documentation is already available on readthedocs. It will be updated for Beijing as needed. |
|
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
SDC | REST API | Currently Available, but needs to be updated to use onap.org | TBD | Link toward the detailed API description |
AAI | REST API | Currently Available | Currently Available | |
CCSDK | OpenDayLight, SLI, |
AAI Client, dblib | TBD | TBD | ||
DMaaP | API to publish/subscribe to events sent for VNF/VM action requests. | Currently Available | Currently Available | DMaaP API |
AAF | Application Authorization Framework | TBD | TBD |
API Outgoing Dependencies
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
---|---|---|---|---|---|
NB Interface | REST API | TBD | 3/8/18 | 3/18/18TBD | Link toward the detailed API description |
...
Name | Description | Version |
---|---|---|
ODL | OpenDaylight controller platform | ?Nitrogen |
Docker | Docker container host | 1.12 |
MariaDB | MariaDB-server Docker data base container | ? TBD |
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.
- R1 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 itemsFunctional testing will occur to ensure that the use cases are functioning correctly.
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.
...
Risk identified | Mitigation Plan | Contingency Plan |
---|---|---|
ODL upgrade to Nitrogen & DB to MariaDB - depends on CCSDK/SDNC to provide dockersprojects | Accept risk | None |
AAF scoping delivery of AAF-91 into Beijingin 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
...
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
- ...
Note | ||
---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
Documentation updates planned for Beijing release are tracked under Documentation Epic: APPC-308
Other Information
Vendor Neutral
...