Target release: Jakarta
Note: this is based on the current ASD concept understanding. This would be a PoC use case to prove ASD usage (onboarding/distribution) and interactions of southbound interfaces (e.g., Kubernetes)
Goals:
- ASD onboarding to SDC, including:
- Allow SDC designers to customize/add custom properties ? e.g., defining input parameters, adding custom properties...
- Store original vendor packages
- Store enhanced ASD descriptors
- 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 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
- demonstrate how internal ASD and Helm Charts are processed by the orchestrator (e.g.
- perform Dry Run in Helm v3
- send requests to Kubernetes
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.
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.
Note:
- ETSI SOL001-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
- SDC 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/CNFD
- Service CSAR includes both vendor ASD and internal ASD
- 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
- SDC creates Service CSAR for the ASD AND ETSI VNF/CNFD
- 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 Service 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 (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 application
- Helm V3 retrieves Helm Charts from the Repository
- Using 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 Processor
- Helm V3 does dry-run before real deployment; i.e., render templates with the right values
- If 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
- Helm V3 does dry-run before real deployment; i.e., render templates with the right values
ASD Package
The following diagram depicts ASD package, conforming to SOL004.
Note: the App (xApp, rApp) package structure will be added here once the specification is available. Most likely, xApp and rApp support is not part of the initial PoC.
SDC Onboarding
- Package Delivery: A vendor delivers an SOL004-based ASD package
- Pre-Onboarding for validation: TBD
- Onboarding: SDC brings in and stores resources such as xNF, xApp and rApp into ONAP for later use in services.
Onboarding Information Flow
SDC needs to support the following onboarding process.
Note: ASD package validation is not addressed here. TBD
SDC Internal Package for ASD
The following depicts SDC internal package for ASD.
- SDC adds an UUID identifier
- SDC adds additional TOSCA Metadata
- SDC transforms ASD into internal models
- SDC can add a license model file
- The user may optionally add additional artifacts manually
Mapping between ASD and SDC internal model
- ASD specification is relatively simple
- Propose to use ASD specification as the SDC internal model
Enhancement of SDC Internal ASD model
- SDC allows SDC designers to customize/add custom properties when it creates internal ASD models
- SDC UI allows the user to define necessary input parameters and add custom resource properties...
- in that case, enhanced ASD can contain most of resource information for the orchestration by SO/Helm v3
- SDC stores the original vendor ASD packages
Package Distribution
The following depicts SDC Service CSAR distribution and storage.
- SDC sends package notifications to DMaaP for its subscribers (Catalog Manager, SO, other ONAP runtime components)
- Catalog Manager queries ASD descriptors once it gets a package notification from SDC via DMaaP
- note: the current ONAP runtime Catalog Manager handles ETSI packages. we may extend it to handle ASD. TBD
- SDC pushes Helm Charts to the target Helm Repository
- SDC pushes Images to the target Image Repository
- Note: SDC will support large-size images
- Catalog Manager, Helm Repository and Image Repository are centralized in the PoC. Domain-specific repositories will be considered in the future.
LCM Orchestration
TBD
Interfaces
SDC Onboarding
- SDCE-1
SDC and Catalog Manager
- TBD
- should we leverage the Model_catalog component which was designed for ETSI package???
SDC and Helm Repository
- TBD
SDC and Image Repository
- TBD
OSS/BSS (or SO Client) and SO
- SO NBI
SO and Helm Processor
- TBD
Helm Processor and Placement
- TBD
Helm Processor and Helm Client
- TBD
Helm Client and O-Cloud (K8S)
- Kubernetes APIs
Components (Functions and Requirements)
Helm Repository
Image Repository
Helm Processor
Placement
Target release: Jakarta
Note: this is based on the current ASD concept understanding. This would be a PoC use case to prove ASD usage (onboarding/distribution) and interactions of southbound interfaces (e.g., Kubernetes)
Goals:
- ASD onboarding to SDC, including:
- Allow SDC designers to customize/add custom properties ? e.g., defining input parameters, adding custom properties...
- Store original vendor packages
- Store enhanced ASD descriptors
- 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 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
- demonstrate how internal ASD and Helm Charts are processed by the orchestrator (e.g.
- perform Dry Run in Helm v3
- send requests to Kubernetes
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.
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.
Note:
- ETSI SOL001-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
- SDC 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/CNFD
- Service CSAR includes both vendor ASD and internal ASD
- 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
- SDC creates Service CSAR for the ASD AND ETSI VNF/CNFD
- 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 Service 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 (Helm v3)
- SO passes Descriptor (ASD) information and required parameters (e.g., lifecycleParameters) to the Helm Processor
- Helm Processor handles internal 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.
- Use Helm to install the application on a particular cluster with the values constructed in the Helm Processor
- Helm V3 does dry-run before real deployment; i.e., render templates with the right values
- If 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
- Helm V3 does dry-run before real deployment; i.e., render templates with the right values
ASD Package
The following diagram depicts ASD package, conforming to SOL004.
Note: the App (xApp, rApp) package structure will be added here once the specification is available. Most likely, xApp and rApp support is not part of the initial PoC.
SDC Onboarding
- Package Delivery: A vendor delivers an SOL004-based ASD package
- Pre-Onboarding for validation: TBD
- Onboarding: SDC brings in and stores resources such as xNF, xApp and rApp into ONAP for later use in services.
Onboarding Information Flow
SDC needs to support the following onboarding process.
Note: ASD package validation is not addressed here. TBD
SDC Internal Package for ASD
The following depicts SDC internal package for ASD.
- SDC adds an UUID identifier
- SDC adds additional TOSCA Metadata
- SDC transforms ASD into internal models
- SDC can add a license model file
- The user may optionally add additional artifacts manually
Mapping between ASD and SDC internal model
- ASD specification is relatively simple
- Propose to use ASD specification as the SDC internal model
Enhancement of SDC Internal ASD model
- SDC allows SDC designers to customize/add custom properties when it creates internal ASD models
- SDC UI allows the user to define necessary input parameters and add custom resource properties...
- in that case, enhanced ASD can contain most of resource information for the orchestration by SO/Helm v3
- SDC stores the original vendor ASD packages
Package Distribution
The following depicts SDC Service CSAR distribution and storage.
- SDC sends package notifications to DMaaP for its subscribers (Catalog Manager, SO, other ONAP runtime components)
- Catalog Manager queries ASD descriptors once it gets a package notification from SDC via DMaaP
- note: the current ONAP runtime Catalog Manager handles ETSI packages. we may extend it to handle ASD. TBD
- SDC pushes Helm Charts to the target Helm Repository
- SDC pushes Images to the target Image Repository
- Note: SDC will support large-size images
- Catalog Manager, Helm Repository and Image Repository are centralized in the PoC. Domain-specific repositories will be considered in the future.
LCM Orchestration
TBD
Interfaces
SDC Onboarding
- SDCE-1
SDC and Catalog Manager
- TBD
- should we leverage the Model_catalog component which was designed for ETSI package???
SDC and Helm Repository
- TBD
SDC and Image Repository
- TBD
OSS/BSS (or SO Client) and SO
- SO NBI
SO and Helm Processor
- TBD
Helm Processor and Placement
- TBD
Helm Processor and Helm Client
- TBD
Helm Client and O-Cloud (K8S)
- Kubernetes APIs