Versions Compared

Key

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

...

Interface NameDefinitionCapabilitiesVersionStatusPayload Model(s)
SO-E-01Service 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 KeyAPI Interface NameDescription
SDCE-6Service/Resource model notification
POE-5Delegation of decision to policy logic
OOF-HAS-??Delegation of placement decision
AAIE-1Ingest/update state of services and resources
MCE-2

Assign and configure infrastructure resources

CONE-3Assign and configure resources
APPC-??Assign and configure resources
(Using APPC library hosted in BPEL)
[Yang, REST, DMaaP]
VFCE-2Network Service LCM
SOL003Delegation of orchestration to VNFM
SDCE-7Service/Resource model query

...

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

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 BPEL Execution Engine. The BEPL 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

...