You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Note: Work in Progress

Epic

EpicDescriptionJIRA
SO and its sub-components, CNFM, CNF Adapter, shall support ASD-based CNF lifecycle orchestration

SO and its sub-components, CNFM, CNF Adapter, shall support ASD-based CNF lifecycle orchestration

  • Create
  • Instantiate
  • Terminate
  • Delete







User Story

User StoryDescriptionJIRA
SO shall get ASD-based CNF package from SDC and store it metadata to SO Catalog DB

SO shall get the ASD-based CNF package from SDC and store it metadata to SO Catalog DB.

  • Distinguish the ASD-based CNF package based on package metadata

SO shall process model info and decide flows

SO shall process model info and decide flows

  • If the package metadata indicates 'ASD', SO shall process ASD-based CNF workflows
  • SO shall create service instance to AAI
  • SO shall resolve parameters
  • SO shall delegate ASD-based CNF orchestration to CNF Manager

< CNF Manager processes requests >

  • After the CNF Manager process, SO shall update CNF to AAI




CNF Manager shall process ASD-based CNF Lifecycle orchestration

CNF Manager shall process ASD-based CNF Lifecycle orchestration

  • CNF Manager shall process input parameters from SO
  • CNF Manager shall get enhanced ASD (descriptor) and artifacts from the ASD repository Manager
  • CNF Manager shall get associated Helm Charts from the Helm Repository Manager
  • CNF Manager shall decompose ASD and get the associated DeploymentItems list
  • CNF Manager shall transform ASD cloud artifacts with parameters to K8S resource description (e.g., helm template or helm install --dry-run)
  • CNF Manager shall get placement information by passing K8 resources + ASD' + additional data to the Placement
  • CNF Manager shall make a placement decision based on input data & return it
  • Per DeploymentItem, CNF Manager shall send (with cluster id, parameter, cloud artifacts) to K8S (e.g., helm install ...)
    • note: it is possible to leverage the CNF Adapter for the connection to K8S Plugin




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

ONAP ComponentDescription
AAIRequired for Inventory Cloud Owner, Customer, Owning Entity, Service, Generic VNF, VF-Module
SDCVSP, VF and Service Modeling of the ASD-based CNF
SORequired for Macro Orchestration using the generic building blocks
CNF Adapter
SDNCProvides GENERIC-RESOURCE-API for cloud instantiation orchestration via CDS
Policyused to store naming policy
Portalrequired to access SDC
CDSTBD
CNFM
MultiCloudTBD
Runtime Catalog Mgr
Helm Artifact Repository
Image Artifact Repository

Input Parameter Handling


Helm Data Processing Flow

  • No labels