...
For the purpose of illustration of the ASD model, this example uses a YAML mapping of the descriptor model.
sample-app-asd.yaml
kind: ASD |
---|
The deployment order parameters “deploymentItems” above, the “sampleapp-db-operator” chart will be deployed first, followed by the “sampleapp-services” chart, since they are labelled for consecutive deployment orders. If both charts were to be deployed in parallel, the value of deploymentOrder would be set to 1.
...
editor note: placeholder for helm chartcharts
- sampleapp-db-operator-helm.tgz
- sampleapp-services-helm.tgz
...
ASD yaml file at the root of the archive as the CSAR Entry-definition file example:
MyCompanyASD.yaml file:
tosca_definitions_version: tosca_simple_yaml_1_3 |
---|
In this example, “asd_definitions” is introduced as a new key name to metadata. Thus, it will be required to be either define or register with either ETSI NFV SOL004 or with OASIS TOSCA TC.
Below figure is an example of CSAR including the ASD (sample-app-asd.yaml), a main TOSCA definition YAML file metadata only (MyCompanyASD.yaml), signature file, manifest, certificate, deployment artifacts, and images.
├── MyCompanyASD.yaml |
---|
The two referenced deployment artifacts are contained in the “deployment_artifacts” directory, and the package also contains two container images in OCI format, in the “images” directory.
The corresponding manifest file:
, sample-app.mf, shows:
metadata: |
---|
Example processing flow of an ASD
...
- Orchestrator shall support the capability to use the deployment parameters from ASD for the application or CNF deployment. These deployment parameter values shall correspond to the parameters defined in the “lifecycleParameters” section(s) of the ASD.
- Orchestrator shall support the capability to construct a values file from instance specific parameter values provided at deployment time, and default values supplied in the chart.
- Orchestrator shall support the capability to perform a chart render into concrete K8S resource descriptions.
- Container resource management for determining placement for CNF application on certain K8S cluster(s), orchestrator shall support the capability to parse the workload descriptors and extract those values.
Revision History:
July 26,2021: initial draft
July 28,2021: editorial clean fixing example snipped code format