Table of Contents |
---|
Target release: Jakarta (it could be changed)
Helm 3 Interaction between Helm Client and Kubernetes API Server
Helm 3 has a client-only architecture with the client. In Helm 3, the client interacts directly with the Kubernetes API server The in-cluster server Tiller is removed.
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
ASD Onboarding and Orchestration PoC Architecture
The architecture conforms to the above Helm3 client-only architecture.
The following diagram depicts ASD onboarding and orchestration PoC.
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
Note:
- ETSI-based model orchestration leveraging Helm Processor needs to be sort out further.
- Helm Processor realization (e.g., MultiCloud??, EMCO?? others??) will be discussed
- Placement realization (e.g., OOF?? others??) will be discussed
Sequence Steps:
- Onboard package – this will ingest the package, and verify the integrity and authenticity of the package etc.
- SDC supports ASD packages in addition to ETSI packages
- both ASD and ETSI packages conform to ETSI SOL004
- Store relevant information in repo – for internal organization and making the package available for deployment.
- SDC creates Service CSAR for the ASD AND ETSI VNF/CNFD
- Descriptors will be stored in the Catalog Manager Repository
- Helm Charts will be stored in the Helm Repository
- Images will be stored in the Image Repository
- Receive deployment order, along with required parameters. The required parameters are the ones specified in the ASD under “lifecycleParameters”.
- SO receives incoming Service Requests and retrieves the corresponding Service Catalog
- So validates required parameters
- Fetch descriptors from package.
- SO decomposes incoming Service Requests into Resources
- If the resource is for CNF and ASD-based models, SO follows the ASD orchestration path
- If the resource is for ETSI-based models, SO delegates its orchestration to SO NFVO or VFC
- SO delegates ASD orchestration to the Helm Processor
- SO passes Descriptor (ASD) information and required parameters (e.g., lifecycleParameters) to the Helm Processor
- Helm Processor handles ASD-based NF or application
- Helm Processor retrieves Helm Charts from the Repository
- 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.
- 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.
- 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.
- Use Helm to install the application on a particular cluster with the values constructed in the Helm Processor
- Helm Processor do dry-run before sending its requests to K8S
Interfaces
SDC Onboarding
SDC and Catalog Manager
SDC and Helm Repository
SDC and Image Repository
OSS/BSS and SO
SO and Helm Processor
Helm Processor and Placement
Helm Processor and Helm Client
Helm Client and O-Cloud (K8S)