Project Overview
The ONAP SO provides the highest level of orchestration functionality in the ONAP platform.
New component capabilities for Dublin, i.e. the functional enhancements
SO will contribute to the following use cases as part of the functional requirements.
- VNFM SOL003 adapter support : Resources commitment from Ericsson and Nokia
- CCVPN extension : Resources commitment from CMCC, VDF, ZTE.
- Change Management Extension : Commitment based on support from ATT resources.(Scope TBD)
- PNF extension : Resource commitment from Nokia.
- HPA extension (Hardening) for the other existing usecases : Support from Intel
- Support Multi Cloud for cloud agnostic orchestration : Support from Intel and VMware.
- Consistent ID of a cloud region : Support from ATT (Testing effort)
- Internal architecture improvements and work towards modularity:
- So Monitoring pagination
- S3P
- Documentation improvements
- UT and CSIT improvements
- BBS : Resource commitment under discussion (Nokia/Huawei/Swisscom??).
- 5G Support : (Under discussion ATT/Intel/vmware/Ericcson/Amdocs??)
- Removal of Manual interventions : (Under discussion Tech mahindra, ATT...??)
- SOL005 adapter support : Resources from Verizon (under discussion of the usecsase to be used is not yet clear)
A new Microservice for the VNFM Adapter will be added to the SO as a separate pod
SO would be upgraded to the Spring boot 2.0
- SO should support the workflows designed in SDC (extension from the R3 Release)
- SO should support List type for resource orchestration
New or modified interfaces
- Interfaces added in Dublin:
- For the Change management feature
- VNF InPlaceSoftwareUpdate
- VNF ConfigUpdate
Update Service (Add site)
- Interfaces added in Dublin:
Interface naming
- REST interfaces with various APIs for the three DMaaP components. Details of the API signatures at the links belownew APIs of Change Management:
- VID-SO WFD API – VNF InPlaceSoftwareUpdate
- VID-SO WFD API – VNF ConfigUpdate
- Details of the APIs modified for the CCVPN :
- Update Service Instance
- REST interfaces with various APIs for the three DMaaP components. Details of the API signatures at the links belownew APIs of Change Management:
Reference to the interfaces
What are the system limits
Involved use cases, architectural capabilities or functional requirements
SO will contribute to the following use cases as part of the functional requirements.
- BBS Broadband Service Use Case (Dublin)
- Continuation of HPA (Dublin) - Extension to R3
- Listing of new or impacted models used by the project (for information only)
.None
.