...
Sequence Steps:
# | Actor | Action |
1 | Designer•Design |
|
2 | Designer / SDC•Onboard |
|
3 | SDC•Distribute |
|
4 | SO Client•Start |
|
5 | SO•S1 |
|
6 | CNF Manager•Retrieve |
|
7 | CNF Manager•Retrieve |
|
CNF Manager•Transform |
| |
8,9 | CNF Manager |
|
9 | Placement |
|
10 | CNF Manager•Send |
|
11 | k8S•Retrieve |
|
12 | SO |
|
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 packagesboth ASD and ETSI packages conform to ETSI SOL004SDC transforms vendor ASD to internal ASD (proposal: ASD specification = internal ASD specification)
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/CNFDService CSAR includes both vendor ASD and internal ASD
Descriptors will be stored in the Catalog Manager RepositoryHelm Charts will be stored in the Helm RepositoryImages 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 CatalogSo validates required parameters
Fetch descriptors from Service package.SO decomposes incoming Service Requests into ResourcesIf the resource is for CNF and ASD-based models, SO follows the ASD orchestration pathIf the resource is for ETSI-based models, SO delegates its orchestration to SO NFVO or VFC
SO delegates ASD orchestration to the Helm Processor (Helm v3)SO passes Descriptor (ASD) information and required parameters (e.g., lifecycleParameters) to the Helm Processor
Helm V3 handles internal ASD-based NF or applicationHelm V3 retrieves Helm Charts from the RepositoryUsing received parameters and default values already in the chart to construct the value files (custom yaml files and will be stored in the database).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.Use Helm to install the application on a particular cluster with the values constructed in the Helm ProcessorHelm V3 does dry-run before real deployment; i.e., render templates with the right valuesIf generating the manifest and verifying the YAML file are only purpose, helm template can be considered
If dry-run is satisfied, Helm V3 sends its requests to K8S
...