Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Drawio
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameService Orchestrator Component Description
simpleViewerfalse
width
diagramWidth9011030
revision25

2. API Definitions

2a. Exposed APIs

API KeyAPI NameDescriptionPayload Model(s)Status
SO-E-01
Service and Resource order requests

2b. Consumed APIs

API KeyAPI NameDescription
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

Please see the TOSCA Policy Primer page for an introduction to TOSCA policy concepts. See the Policy Design and API flow page for a description of the component interactions. 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

...

6. System Deployment Architecture

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

IMAGE
onap/so/bpmn-infra
onap/so/so-monitoring
onap/so/api-handler-infra
onap/so/sdnc-adapter
onap/so/vfc-adapter
onap/so/openstack-adapter
onap/so/sdc-controller
onap/so/request-db-adapter
onap/so/catalog-db-adapter
mariadb:10.1.11


7. New Release Capabilities

...