| Table of Contents |
|---|
- ASD PoC Target release:
...
- Kohn
- PoC is now completed!!
- ASD Contribution Target release: London
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)
POC Outcome and Presentation
- Presentation at the LFN DTF November, Seattle USA:
CloudNativeOrchestrationUsingASD-11-18-2022-Final.pdf
See the https://wiki.lfnetworking.org/pages/viewpage.action?pageId=80281744 for recording
- Sample free5gc ASD package:
ASD Design & Orchestration Overview
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
- use the ASD model as SDC internal model (TBD_
- leverage SDC Multi Model support feature, creation of distinct notification for ASD, ETSI and HEAT...
- 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
- Resolve K8 resources based on input parameters and Cloud Artifacts
- send requests to Kubernetes
...
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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
Diagram for Jakarta
Gliffy macroId b714f8c2-f5c2-49b4-b67a-9b29a3375d80 name ASD onboarding and distribution - Jakarta pagePin 1
helm install --dry-run or --debug vs. helm template
...
The following process depicts the ASD-based CNF orchestration scenario., leveraging CDS (future consideration)
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Based on the example of the ONAP webpage, https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=10342219516478029
Some Underlying Data and Node Types
...
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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
...
Based on the example of the ONAP webpage, https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=10342219516478029
Some Underlying Data and Node Types
...
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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
...
Based on the example of the ONAP webpage, https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=10342219516478029
Some Underlying Data and Node Types
...