Status: DRAFT
Service Orchestrator:
1. High Level Component Definition and Architectural RelationshipsÂ
2. API Definitions
2a. Exposed APIs
| Interface Name | Definition | Capabilities | Version | Status | Payload Model(s) |
|---|---|---|---|---|---|
| SO-E-01 | Service and Resource order requests | Service Instance management Health check, global and node. Infrastructure provider management (SO perspective) Infrastructure management | 3.1.2 | Embedded in interface |
2b. Consumed APIs
| API Key | API Name | Description |
|---|---|---|
| SDCE-6 | Service/Resource model notification | |
| POE-5 | Delegation of decision to policy logic | |
| OOF-HAS-?? | Delegation of placement decision | |
| AAIE-1 | Ingest/update state of services and resources | |
| MCE-2 | Assign and configure infrastructure resources | |
| CONE-3 | Assign and configure resources | |
| APPC-?? | Assign and configure resources (Using APPC library hosted in BPEL) [Yang, REST, DMaaP] | |
| VFCE-2 | Network Service LCM | |
| SOL003 | Delegation of orchestration to VNFM | |
| SDCE-7 | Service/Resource model query |
3. Component Description
Orchestration is the execution of various modules capabilities in harmony as a consolidated process to accomplish the desired tasks. The Service Orchestrator (SO) component of ONAP provides orchestration at a very high level, with an end to end view of the infrastructure, network, and applications.
SO's primary function is the automation of end-to-end service instance provisioning activities. SO is responsible for the instantiation and configuration of VNFs in support of overall end-to-end service instantiation, operations and management. SO executes well-defined processes to complete its objectives and is typically triggered by the receipt of service requests generated by other ONAP components or by Order Lifecycle Management in the BSS layer. The orchestration procedure is obtained from the Service Design and Creation (SDC) component of ONAP, where all service designs are created and exposed/distributed for consumption
4. Known System Limitations
https://docs.onap.org/en/dublin/submodules/so.git/docs/release-notes.html
5. System Deployment Architecture
7. New Release Capabilities
Support CCVPN extension
Support BroadBand Service Usecase
SO SOL003 plugin support
Improve PNF PnP
Improve SO internal modularity
8. References
- Interfaces
Known system limitations
- Deployment information