...
Interface Name | Definition | Capabilities | Version | Status | Payload Model(s) | API Spec (Swagger) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SO-E-01 | Service and Resource order requests | Service Instance management management (Service, Volume Group, VF Module, VNF) draw.io Diagram | border | true | true | fitWindow | false | diagramName | Service Orchestrator Component Description | simpleViewer | false | diagramWidth | 1494 | revision | 1 | Health check, global and node. Infrastructure provider management (Certificates, networks, sub-networks, security groups) | 3.1.2 | Production | Embedded in interface |
2b. Consumed APIs
Interface Name | Description | API Spec (Swagger) |
---|---|---|
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 network resources | |
APPC | Assign and configure resources (Using APPC library hosted in BPMN) [Yang, REST, DMaaP] | |
VFCE-2 (SOL005) | Delegation of Network Service LCM | |
SOL003 | Delegation of VNF LCM 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.
...
- Interfaces: https://docs.onap.org/en/dublin/submodules/so.git/docs/api/offered_consumed_apis.html
Known system limitations: https://docs.onap.org/en/dublin/submodules/so.git/docs/release-notes.html
- Deployment information: https://docs.onap.org/en/casablanca/submodules/so.git/docs/developer_info/Working_with_SO_Docker.html
Attachments list |
---|