Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

JIRA:

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-1043

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 (deployment and configuration)

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3808







User Story

PriorityUser StoryAffected ComponentDescriptionJIRA
1SO shall get the ASD-based CNF package from SDC and store its metadata to SO Catalog DB

SDC Controller,

CatalogDB Adapter,

CatalogDB

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

Task:

Pre Condition:

  • SO  SDC Controller, CatalogDB Adapter and CatalogDB component instances are running and ready to get SDC notifications

Post Condition:

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

  • 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.

  • Task: SO distinguishes the ASD-based CNF package based on the package metadata, 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

2For ASD-based CNF provisioning, SO shall process model info and decide flows

API Handler,

RequestDB Adapter,

RequestDB,

SO BPMN Infra, 

AAI

SO shall process ASD model info and decide ASD provisioning flows

Pre Condition:

  • SO CatalogDB contains ASD Model metadata
  • SO Client provides parameters based on the ASD lifecycleParameter list

Post Condition:

  • CNF Manager receives requests from SO BPMN Infra and processes the requests
  • After the CNF Manager process, SO shall update CNF to AAI

Task: 
  • Create & Configures ASD-based CNF workflows
    • Create new BPMN workflows for ASD-based CNF workflows
    • Configure SO MacroFlows for ASD-based CNF workflows

Task:

  • 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
    • no change

Task: 

  • 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

Task:

  • SO shall create service instance to AAI
    • note: leverage AAI schema service; no code impact

Task:

  • 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 AAI

    3CNF Manager shall process ASD-based CNF Lifecycle orchestration

    SO CNFM,

    ASD Repository,

    Helm Artifact Repository,

    OOF,

    AAI, 

    SDNC Adapter,

    SDNC,

    CDS,

    CNF Adapter

    CNF Manager shall process ASD-based CNF Lifecycle orchestration

    Pre Condition:

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

    Post Condition:

    • ASD-based CNF is provisioned by CNF Manager

    Note: PoC, ASD external CPDs will not be handled (TBD)


    Task: 

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

    Task:

    • CNF Manager shall support the capability to process input 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.

    Task:

    • CNF Manager shall communicate with the ASD Repository to get ASD (descriptor) and artifacts from the ASD repository Manager.
      • CNF Manager shall decompose ASD and get the associated DeploymentItems list

    Task:

    • CNF Manager shall get associated Helm Charts from the Helm Repository Manager.

    Task:

    • CNF Manager shall support 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.

    Task:

    • CNF Manager shall transform ASD cloud artifacts with parameters to K8S resource description (e.g., helm template or helm install --dry-run)

    Task:

    • 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)

    Task:

    • CNF Manager shall make a placement decision based on the decision from the Placement component.

    Task:

    • 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 ...)
      • SO CNF Adapter APIs are being studied. 

    Task:

    • CNF Manager shall CNF instance to AAI

    Note: PoC, ASD external CPDs will not be handled (TBD)

    Post Condition:

    ASD-based CNF is provisioned by CNF Manager

    4AAI shall support CRUDQ of ASD-based CNF ResourcesAAI

    AAI shall support CRUDQ of ASD-based CNF Resources

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

    Overall Process

    • Pre-Conditions
      • 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
    • ASD-Based CNF LCM Orchestration
      • 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

    ...