...
Project Name | Enter the name of the project |
---|---|
Target Release Name | Enter the name of the release you are targeting to deliverBeijing Release |
Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
Participating Company List | the company participating in this release. At least 3-4 organizations, including an operator are recommended.AT&T, Intel, Tech Mahindra |
Scope
What is this release trying to address?
...
The Beijing Release will be focusing on Platform Maturity as a priority. Additional LCM actions will be added to the scope of APIs supported. These additional LCM actions have already been developed and validated by AT&T and will be contributed to ONAP.
More specifically, APPC will focus on the following areas in Beijing.
- Remove references and use of openecomp and replace with onap
- Address S3P requirements to the extent possible to comply with minimum requirements requested for Beijing for areas not already at this level.
- Notes:
- Compliancy for Performance Level 1 is still being investigated
- Compliancy for Stability is assumed to be addressed by Integration team system level testing
- Resiliency -
- Local HA: this is a function of ODL clustering capability, so whatever is supported by ODL Nitrogen defines local HA capabilities
- Geo-red: manual site failover only will be supported in Beijing
- Notes:
- Support AAF (Authentication and Authorization Framework) for API access
- Upgrade ODL version to Nitrogen (driven by CCSDK dependency)
- Replace MySQL with MariaDB (driven by CCSDK 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
- Following Actions in support of In-place software upgrade
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
...
API this project is delivering to other projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
Third Party Products Dependencies
...