You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

The following diagram depicts ASD onboarding and orchestration PoC.

Target release: Jakarta (it could be changed)


ASD onboarding and orchestration PoC

Sequence Steps:

  1. Onboard package – this will ingest the package, and verify the integrity and authenticity of the package etc.
    1. SDC supports ASD packages in addition to ETSI packages
    2. both ASD and ETSI packages conform to ETSI SOL004
  2. Store relevant information in repo – for internal organization and making the package available for deployment.
    1. SDC creates Service CSAR for the ASD AND ETSI VNF/CNFD
    2. Descriptors will be stored in the Catalog Manager Repository
    3. Helm Charts will be stored in the Helm Repository
    4. Images will be stored in the Image Repository
  3. Receive deployment order, along with required parameters. The required parameters are the ones specified in the ASD under “lifecycleParameters”.
    1. SO receives incoming Service Requests and retrieves the corresponding Service Catalog
    2. So validates required parameters
  4. Fetch descriptors from package.
    1. SO decomposes incoming Service Requests into Resources
    2. If the resource is for CNF and ASD-based models, SO follows the ASD orchestration path
    3. If the resource is for ETSI-based models, SO delegates its orchestration to SO NFVO or VFC
    4. SO delegates ASD orchestration to the Helm Processor
  5. Using received parameters and default values already in the chart to construct the value files. With this input Helm performs a chart render, i,e. translates the charts into concrete K8S resources descriptions.
  6. In the placement use case, the concrete K8S workload description (pod, daemonset, deployment, replicaset, statefulset, job, cronjobs, etc) and the ASD will be used by internal logic of orchestrator for placement decision.
  7. Perform placement decision – the placement function can parse the workload descriptors and ASD and use that information to select the appropriate cluster in the selected O-Cloud.
  8. Use Helm to install the application on a particular cluster with the values constructed in step 5.
  • No labels