ASD-Based CNF Orchestration PoC

Note: Work in Progress

Epic

User Story

Overall Process

• SDC accepts onboarding App packages, including ASD and DeploymentItems models, Helm Charts, Images and other artifacts, what allows to keep decomposition of Service instance
• SO subscribes and receives package notifications from SDC
• Based on the notifications, SO ASDC Controller queries for the App packages from SDC, and stores models and artifacts to SO Catalog Database
• MACRO workflow in SO is used for orchestration

ASD-Based App Package Type

• ASD-Based App Package will have the main manifest file, which contains asd-based app package-specific metadata as follows:
  • oran_id
  • oran_product_name
  • oran_provider_id
  • oran_package_version
  • oran_release_date_time
  • oran_entry_definition_type [ "asd", "app", "app-asd", ...]
• SO distinguishes the App package based on the "oran_entry_defintion_type" metadata.
  • If it is "asd", SO will treat it as ASD-based CNF.
  • SO delegates the ASD-based CNF orchestration to the CNF Manager

• x

AAI Data Model

SO ASDC Controller Handling

ASDC Controller Enhancement

SO Catalog DB Enhancement

VF-VF-Module-Helm Package

• During SDC onboarding, the ASD is mapped to VF, and the DeploymentItems is mapped to Vf-Module
• SO expects ASD VSP onboarding packages has the Native Helm, without Dummy Heat.
• VF is split into multiple vf-modules. each vf-module is dedicated to one Helm package. 
  • each Helm application after instantiation is visible to ONAP as a separate vf-module

Deployment Components

note: the current CNFO; will be changed for ASD-based CNF orchestration

Input Parameter Handling