Versions Compared

Key

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

...

Gliffy Diagram
macroIdd59118dd-ceea-44f1-a895-ac1d53ec5145
displayNameASD package structure
nameASD package structure
pagePin12

SDC Onboarding

SDC onboarding process will be enhanced to handle ASD.

...

    • SDC sends package notifications to DMaaP for its subscribers (Catalog Manager, SO, other ONAP runtime components)
    • Catalog Manager queries ASD descriptors once it gets a package notification from SDC via DMaaP
      • note: the current ONAP runtime Catalog Manager handles ETSI packages. we may extend it to handle ASD. TBD
    • SDC pushes Helm Charts to the target Helm Repository
    • SDC pushes Images to the target Image Repository
      • Note: SDC will support large-size images
    • Catalog Manager, Helm Repository and Image Repository are centralized in the PoC. Domain-specific repositories will be considered in the future.

LCM Orchestration

...

The following diagram depicts ASD orchestration for LCM.

Gliffy Diagram
macroId220b0f20-8071-409e-8ae9-4fcfd8d930f1
displayNameASD Deployment flow
nameASD Deployment flow
pagePin4

  1. A deployment order is received, along with the required parameter values
  2. The cloud-native deployment tool is invoked with the received parameters to transform the cloud artifacts into K8S resource descriptions
  3. The K8S resource descriptions, ASD and any other relevant data is sent to the placement function

  4. Placement decision is done based on input data

  5. Inform deployment of placement

  6. Request the cloud native deployment tool to deploy on the identified target cluster

  7. Cloud native deployment tool deploys application in the chosen cluster using the K8S API


Component Functional Enhancements

...