...
- 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
- Dependency on AAF project to provide feature (AAF-91) to enable AAF security on the web server level (jetty level).
- 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
- Additional LCM actions including:
- ActionCancel
- ActionStatus
- AttachVolume
- DetachVolume
- Following Actions in support of In-place software upgrade
- CDT Tool - an APP-C Design Tool enabling VNF owners to create templates and other artifacts for APP-C Configure command (used to apply a post-instantiation configuration) as well as other life cycle commands.
- Documentation updates for Beijing
...
List the other ONAP projects you depend on.
APPC interacts and has dependencies on the following components as part of the general ONAP architect
- 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 AAPC APPC currently must align on ODL version.
- AAF - AAF is used for authentication of APIs
For the Beijing release have , APPC has dependencies on the following two projects to deliver updated components:
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||
|---|---|---|---|---|---|---|
| SDC | REST API | TBD | TBD | Link toward the detailed API description | ||
| AAI | REST API | |||||
| CCSDK | OpenDayLight, SLI, and AAI Client | |||||
| DMaaP | API to publish/subscribe to events sent for VNF/VM action requests. | DMaaP API | ||||
| AAF | Application Authorization Framework |
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| NB Interface | REST API | TBD | TBD | Link toward the detailed API description |
Third Party Products Dependencies
...
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended recommended to provide these agreements and dates in this section.
...