Page History

SDC Controller,

CatalogDB Adapter,

CatalogDB

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
• Store the ASD-based CNF package metadata and artifacts to SO Catalog DB

API Handler,

RequestDB Adapter,

RequestDB,

SO BPMN Infra, 

AAI

SO shall process ASD model info and decide ASD provisioning flows

• SO BPMN Infra decomposes Service into VF Resource(s)
• If the VF resource metadata indicates 'ASD', SO shall process ASD-based CNF workflows
  • Configure SO MacroFlows
  • New BPMN workflows for 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
  • Pass input parameters

< CNF Manager processes requests >

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

SO CNFM,

ASD Repository,

Helm Artifact Repository,

OOF,

AAI, 

SDNC Adapter,

SDNC,

CDS,

CNF Adapter

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