Page History

...

• ASD onboarding to SDC, including:
  • ASD integration with Service Model in SDC, including internal mapping
    • Proposal: use the ASD model as SDC internal model
  • Allow SDC designers to customize/add custom properties ? e.g., defining input parameters, adding custom properties...
  • Store original vendor packages
  • Transforming onboarding ASD packages into internal ASD model
    • Proposal: use the ASD model as SDC internal model
• ASD integration with Service Model in SDC
• SDC distribution to ONAP Runtime components
  • Store ONAP internal ASD Descriptors in Catalog Manager
  • Store Helm Charts in Helm Chart Repository
  • Store Images in Image Repository
• Orchestration based on internal ASD-model
  • Orchestrators (Helm v3) get Helm Chart
  • information
  • not repeating resource information that is defined in Helm Charts
  demonstrate how internal ASD and Helm Charts are processed by the orchestrator orchestrator (e.g.
  • perform Dry Run in Helm v3

Helm 3 Interaction between Helm Client and Kubernetes API Server

...

Note:

1. ETSI-based model orchestration leveraging Helm Processor needs to be sort out further. 
2. Helm Processor realization (e.g., MultiCloud??, EMCO?? others??) will be discussed
3. Placement realization (e.g., OOF?? others??) will be discussed

...

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
   3. SDC transforms vendor ASD to internal ASD
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 Service 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
5. SO delegates ASD orchestration to the Helm Processor (Helm v3)
   1. SO passes Descriptor (ASD) information and required parameters (e.g., lifecycleParameters) to the Helm Processor
6. Helm Processor handles internal ASD-based NF or application
   1. Helm Processor retrieves Helm Charts from the Repository
   2. Using received parameters and default values already in the chart to construct the value files.
   3. With this input Helm performs a chart render, i,e. translates the charts into concrete K8S resources descriptions.
7. 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.
8. 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.
9. Use Helm to install the application on a particular cluster with the values constructed in the Helm Processor
   1. Helm Processor do dry-run before sending its requests to K8S

...