Key Contacts - Byung-Woo Jun (Ericsson)
ASD PoC Presentation Status Demo:
Requirement Proposal:
ASD Overview:
What?
- Deployment descriptor for cloud native applications / functions
- Minimum information needed for the Orchestrator
- References to the cloud native artifacts
- CAR package adhering to ETSI SOL004
Why
- Minimize duplication
- Use Kubernetes management capabilities
- Clean separation between high-level orchestration and cloud native application deployment
Business Driver
- ORAN
- Reference implementation in ONAP
ASD Orchestration Goals:
- Service CSAR with ASD resources distribution to ONAP runtime thru DMaaP
- Preserving the vendor ASD CSAR inside Service CSAR
- Proving Query APIs for ASD, Helm Charts and Image artifacts
- SO Orchestration for ASD-Aligned CNFs/Apps
- Create / Instantiate / Terminate / Delete AS operations
- External K8s Clusters registration
- AS topology inventories (Generic VNF / VF-Modules / K8s Resources)
- Deploy associated Helm Charts to a selected K8s cluster, based on ASD definitions and User Input
Architecture:
Overview:
The following diagram depicts its high-level architecture:
ASD Onboarding to ONAP SDC:
The following diagram depicts the ASD onboarding to ONAP SDC:
ASD Model Transitions in ONAP
The following diagram depicts the ASD Model Transitions in ONAP:
ASD Orchestration By ONAP SO
The following diagram depicts the ASD Orchestration by ONAP SO:
SO CNFM, an SO Plug-in Component
The following diagram depicts the SO CNFM, an SO Plug-in component:
ASD-Based Package Type
- The Resource VF(s) in the onboarded Service CSAR will have the following resource main manifest file
- application_name
- application_provider
- release_date_time
- entry_definition_type [ "asd"]
- SO distinguishes the App package based on the "entry_defintion_type" metadata.
- If it is "asd", SO will process the package as the ASD-based CNF.
- SO delegates the ASD-based CNF orchestration to the CNF Manager