Page History

SDC Controller,

CatalogDB Adapter,

CatalogDB

SO shall get the ASD-based CNF package (SDC Service CSAR) from SDC and store it its metadata to SO Catalog DB.

Task:

• When SO gets a package notification from DMaaP, SO SDC Controller queries SDC for the ASD-based CNF Service CSAR that embeds the ASD-based CNF Resource VF.
• SO distinguishes Distinguish the ASD-based CNF package based on the package metadataStore , and stores the ASD-based CNF package metadata and artifacts to SO Catalog DB

Post Condition:

• SO Catalog DB contains the ASD-based CNF package metadata and artifacts

API Handler,

RequestDB Adapter,

RequestDB,

SO BPMN Infra, 

AAI

SO shall process ASD model info and decide ASD provisioning flows

Pre Condition:

• SO Client provides parameters based on the ASD lifecycleParameter list

Task:

• Create & Configures ASD-based CNF workflows
  • Create new
• 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

• • Configure SO MacroFlows for ASD-based CNF workflows
• SO API Handler receives a service (or a la carte) request for ASD-based CNF and stores the request information into the Request DB
  • Note: expect no change
• SO BPMN Infra decomposes Service into VF Resource(s) and per VF resource, SO BPMN process resource handling
  • If the VF resource metadata indicates the ASD-based VF, SO shall process ASD-based CNF workflows
  • SO shall create service instance to AAI
    
    • note: leverage AAI schema service; no code impact
  • SO shall delegate ASD-based CNF orchestration to CNF Manager
    • Pass input parameters including ASD reference Id, LifecycleParameter, etc.

Post Condition:

• CNF Manager processes requests
• After the CNF Manager process, SO shall update CNF to AAIupdate 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

SO CNFM,Pre Condition:

• ASD

• and App onboarding package is stored in the ASD Repository
• Helm Chart(s) are stored in the Helm Artifact Repository

OOF,

AAI, 

SDNC Adapter,

SDNC,

CDS,

• Image(s) are stored in the Image Artifact Repository

Task: 

• CNF Manager shall support its NBI REST Apis to handle requests from SO.

• CNF Manager shall support the capability to process

• CNF Manager shall process input parameters from SOinput parameters from SO, and use the deployment parameters from ASD for the CNF deployment. Those deployment parameter values shall correspond to the parameters defined in the "lifecycleParameters" section(s) of the ASD.
• CNF Manager shall communicate with the ASD Repository to get enhanced ASD (descriptor) and artifacts from the ASD repository Manager.
  • CNF Manager shall decompose ASD and get the associated DeploymentItems list
• CNF Manager shall get associated Helm Charts from the Helm Repository Manager.
• CNF Manager shall decompose ASD and get the associated DeploymentItems listsupport the capability to construct a values file from instance specific parameter values from SO and merge the values with default values from ASD Helm Chart values.
• CNF Manager shall transform ASD cloud artifacts with parameters to K8S resource description (e.g., helm template or helm install --dry-run-run)
• CNF Manager shall get placement information by passing K8 resources + ASD' + additional data to the Placement component such as OOF.
  • Note: Use of OOF could be out-of-PoC-Scope (TBD)
• CNF Manager shall get placement information by passing K8 resources + ASD' + additional data to the PlacementCNF Manager shall make make a placement decision based on input data & return itthe decision from the Placement component.
• Per DeploymentItem, CNF Manager shall send (with cluster id, parameter, cloud artifacts) to SO CNF Adapter for the connection to K8S plugin(e.g., helm install ...)note: it is possible to leverage the CNF Adapter for the connection to K8S Plugininstall ...)
  • SO CNF Adapter APIs are being studied. 
• CNF Manager shall CNF instance to AAI

Post Condition:

• ASD-based CNF is provisioned by CNF Manager

AAI shall support CRUDQ of ASD-based CNF Resources

• Leverage existing AAI APIs
• Investigate any new AAI APIs for ASD-based CNF Resources (TBD)