Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Status: Copied from R6 - Mar, 22, 2020
Component Status: Pending PTL Updates and ArchCom Review

Last Reviewed:

Certified by:

1. High Level Component Definition and Architectural Relationships 

Drawio
bordertrue
diagramNameso_r7
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth1404
revision1


2. API Definitions

2a. Exposed APIs

Interface NameDefinitionCapabilitiesVersionStatusPayload Model(s)API Spec (Swagger)
SO-E-01Service and Resource order requests

Service Instance management (Service, Volume Group, VF Module, VNF)

Drawio
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameService Orchestrator Component Description
simpleViewerfalse
diagramWidth1494
revision1

Health check, global and node.

Infrastructure provider management (Certificates, networks, sub-networks, security groups)

3.1.2ProductionEmbedded in interface

2b. Consumed APIs

Interface NameDescriptionAPI Spec (Swagger)
SDCE-6Service/Resource model notification
POE-5Delegation of decision to policy logic
OOF-HASDelegation of placement decision
AAIE-1Ingest/update state of services and resources
MCE-2

Assign and configure infrastructure resources


CONE-3Assign and configure network resources
APPCAssign and configure resources
(Using APPC library hosted in BPMN)
[Yang, REST, DMaaP]

VFCE-2 (SOL005)Delegation of Network Service LCM
SOL003Delegation of VNF LCM  to VNFM
SDCE-7Service/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.

...

Internally, SO is organized as a set of modules with well defined responsibility. External adapters (SDNC, OpenStack, VFC and SOL003) encapsulate most communication with external systems. Persistence is exposed to other SO modules – not externally, by DB adapters (Catalog and Request). The underlying workflow component resides in the BPMN Execution Engine. The BPMN Execution Engine also interacts with other ONAP systems such as App controllers, AAI and OOF-HAS. Interactions with SNC are hosted by the SDC Controller. Likewise the API Request Handler exposes SOs API for interaction with clients. Finally there is also a monitoring component that allows insight into the execution state of workflows.

4. Known System Limitations

https://docs.onap.org/en/dublin/submodules/so.git/docs/release-notes.html

5. System Deployment Architecture

https://docs.onap.org/en/casablanca/submodules/so.git/docs/developer_info/Working_with_SO_Docker.html

6. New Release Capabilities

Support CCVPN extension

SO ETSI (SOL003, SOL002 and SOL005) plugin support

...

Support the 5G slicing orchestration



7. References

  1. Interfaces: https://docs.onap.org/en/dublin/submodules/so.git/docs/api/offered_consumed_apis.html
  2. Known system limitations: https://docs.onap.org/en/dublin/submodules/so.git/docs/release-notes.html

  3. Deployment information: https://docs.onap.org/en/casablanca/submodules/so.git/docs/developer_info/Working_with_SO_Docker.html

...