Versions Compared

Key

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

...

The new enhancements proposed draw.io DiagrambordertruediagramNamePossible DeploymentsimpleViewerfalselinksautotbstyletoplboxtruediagramWidth1250revision1SO deployment view

Jira
serverONAP Jira
jqlQueryproject = "Service Orchestrator" AND fixVersion = "London Release" AND issuetype = Epic
serverId425b2b0a-557c-3c0c-b515-579789cceedb



1. SO-4048 : SO and its sub-components shall support ASD-based CNF lifecycle orchestration


Supported Features in SO:

  • Create AS
  • Instantiate AS
  • Terminate AS
  • Delete AS

Image Added





2. SO-4037  :  Support 3GPP 28.532 APIs for slicing use case

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 Added

Impact on SO project:

SO macro flow can support 3GPP 28.532 APIs for slicing use case along with the existing 3GPP 28.531 APIs.

Code changes to be done in:
1. SO api-handler
2. BPMN infra
3. cataloged


Impacted components:

SO (Code change)

OOF (Code change)

CDS(Test only)

AAI (Test only)

CDS (Test only)

Multicloud (Test only)

SDC (Test only)

7. References

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

...