Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Status: Updated for

...

Oslo -  
Component Status:

...

 

Last Reviewed:  

Certified by:  

1. High Level Component Definition and Architectural Relationships 


draw.io Diagram
bordertrue
diagramNameso_r13
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth1403
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, PNF and CNF)

Health check, global and node.

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

3.1.2ProductionEmbedded in interfaceSwagger,json
SO-E-02SO maintenance requests

Monitoring of the SO BPMN flows.

Upload of new recipe war files.

8.0.0Development and EvaluationEmbedded in interfaceMonitoring_Swagger.json

2b. Consumed APIs

ONAP component wise details

...

draw.io Diagram
bordertrue
diagramNameinternal Architecture-R13
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth1403
revision1

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/projects/onap-so/en/latest/release-notes.html#release-notes

5. System Deployment Architecture

https://docs.onap.org/projects/onap-so/en/latest/architecture/architecture.html


6. New Release Capabilities

The new enhancements proposed

...

Proposal is to build an O-RAN specific Macro flow-based NSSMF which can integrate with an external NSMF. What’s the difference ??
• Current ONAP slicing use case is using 3GPP 28.531 APIs (Slice-Specific APIs) And we are proposing 3GPP 28.532 APIs (as per Generic Provisioning APIs based on Managed Object Instances (MOI))
• We propose changes in SO Macro flow building blocks to implement slicing workflows

Image RemovedImage Added

Impact on SO project:

...

Multicloud (Test only)

SDC (Test only)

ARC AAI Component Description - New Delhi-R14ARC Service Orchestrator Component Description - New DelhiOslo-R14R15

7. References

  1. Interfaces: https://docs.onap.org/projects/onap-so/en/latest/index.html#master-index

...