Page History

...

JIRA:

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	REQ-1043

Epic

Description

JIRA

priority

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

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-3808

User Story

...

12CNF Manager
User Story Affected Component Description JIRA Priority
SO 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.
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

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

1
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

1
For 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

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

2.1
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

2.2
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

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

2.4
Task:
SO shall delegate ASD-based CNF orchestration to CNF ManagerSO CNFM
Pass input parameters including ASD reference Id, LifecycleParameter, etc.
note: until SO CNFM is ready, use no-opt operations as a place holder

2.5
SO CNFM 3 shall process ASD-based CNF Lifecycle orchestration
SO CNFM,
ASD Repository,
Helm Artifact Repository,
OOF,
AAI,
SDNC Adapter,
SDNC,
CDS,
CNF Adapter
CNF Manager SO CNFM 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
AAI shall support CRUDQ of ASD-based CNF Resources
Leverage existing AAI APIs
Investigate any new AAI APIs for ASD-based CNF Resources (TBD)
Post Condition:
ASD-based CNF is provisioned by CNF ManagerSO CNFM
Note: PoC, ASD external CPDs will not be handled (TBD)
Note: ASD Repository, Helm Artifact Repository, Image Artifact Repository will be handled by another Epic, which is defined in Application Package Distribution

3
Task: Create SO CNFM and make it available in ONAP
Create SO CNFM as an SO sub-component
Make SO CNFM POD is deployable in OOM
Register SO CNFM POD to AAI automatically

3.1
Task: Support for SO CNFM NBI API Handler
SO CNFM shall support its NBI REST Apis
Task:
CNF Manager shall support its NBI REST Apis to handle requests from SO.

3.2
Task:
CNF Manager SO CNFM 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.

3.3
Task:
CNF Manager SO CNFM shall communicate with the ASD Repository to get ASD (descriptor) and artifacts from the ASD repository Manager.

3.4
Task:
SO CNFM CNF Manager shall decompose ASD and get the associated DeploymentItems list
Get HelmChart references from the DeploymentItems

3.5
Task:
CNF Manager By leveraging the obtained HelmChart references, SO CNFM shall get associated Helm Charts from the Helm Repository Manager.

3.6
Task: Create SO CNFM Instance Database Management
Create SO CNFM Database tables
Provides Database Access Objects (DAO) for CRUD for SO CNFM

3.7
Task:
SO CNFM 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.
SO CNFM shall store the generated values file for an instance to SO CNFM database

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

3.9
Task:
CNF Manager SO CNFM 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)
for PoC, it is allowed to choose predefined K8S Clusters

3.10
Task:
CNF Manager SO CNFM shall make a placement decision based on the decision from the Placement component.

3.11
Task:
Per DeploymentItem, CNF Manager SO CNFM shall send (with cluster id, parameter, cloud artifacts) to the SO CNF Adapter for the connection to K8S plugin(e.g., helm install ...)
SO CNF Adapter APIs are being studied.

3.12
Task:
CNF Manager SO CNFM shall update the CNF instance to AAI
4 AAI shall support CRUDQ of ASD-based CNF Resources AAI
, by leveraging AAI APIs

3.13
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

...

Space shortcuts

Page tree

Versions Compared

Old Version 68

New Version 69

Key

Epic

User Story

Overall Process

User Story	Affected Component	Description	JIRA	Priority
SO 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. 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		1
		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.		1
		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		1
For 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		2
		Task: Create & Configures ASD-based CNF workflows Create new BPMN workflows for ASD-based CNF workflows Configure SO MacroFlows for ASD-based CNF workflows		2.1
		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		2.2
		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		2.3
		Task: SO shall create service instance to AAI note: leverage AAI schema service; no code impact		2.4
		Task: SO shall delegate ASD-based CNF orchestration to CNF ManagerSO CNFM Pass input parameters including ASD reference Id, LifecycleParameter, etc. note: until SO CNFM is ready, use no-opt operations as a place holder		2.5
SO CNFM	3	shall process ASD-based CNF Lifecycle orchestration	SO CNFM, ASD Repository, Helm Artifact Repository, OOF, AAI, SDNC Adapter, SDNC, CDS, CNF Adapter	CNF Manager SO CNFM 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 AAI shall support CRUDQ of ASD-based CNF Resources Leverage existing AAI APIs Investigate any new AAI APIs for ASD-based CNF Resources (TBD) Post Condition: ASD-based CNF is provisioned by CNF ManagerSO CNFM Note: PoC, ASD external CPDs will not be handled (TBD) Note: ASD Repository, Helm Artifact Repository, Image Artifact Repository will be handled by another Epic, which is defined in Application Package Distribution		3
				Task: Create SO CNFM and make it available in ONAP Create SO CNFM as an SO sub-component Make SO CNFM POD is deployable in OOM Register SO CNFM POD to AAI automatically		3.1
				Task: Support for SO CNFM NBI API Handler SO CNFM shall support its NBI REST Apis Task: CNF Manager shall support its NBI REST Apis to handle requests from SO.		3.2
				Task: CNF Manager SO CNFM 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.		3.3
				Task: CNF Manager SO CNFM shall communicate with the ASD Repository to get ASD (descriptor) and artifacts from the ASD repository Manager.		3.4
				Task: SO CNFM CNF Manager shall decompose ASD and get the associated DeploymentItems list Get HelmChart references from the DeploymentItems		3.5
				Task: CNF Manager By leveraging the obtained HelmChart references, SO CNFM shall get associated Helm Charts from the Helm Repository Manager.		3.6
				Task: Create SO CNFM Instance Database Management Create SO CNFM Database tables Provides Database Access Objects (DAO) for CRUD for SO CNFM		3.7
				Task: SO CNFM 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. SO CNFM shall store the generated values file for an instance to SO CNFM database		3.8
				Task: CNF Manager SO CNFM shall transform ASD cloud artifacts with parameters to K8S resource description (e.g., helm template or helm install --dry-run)		3.9
				Task: CNF Manager SO CNFM 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) for PoC, it is allowed to choose predefined K8S Clusters		3.10
	Task: CNF Manager SO CNFM shall make a placement decision based on the decision from the Placement component.				3.11
	Task: Per DeploymentItem, CNF Manager SO CNFM shall send (with cluster id, parameter, cloud artifacts) to the SO CNF Adapter for the connection to K8S plugin(e.g., helm install ...) SO CNF Adapter APIs are being studied.				3.12
	Task: CNF Manager SO CNFM shall update the CNF instance to AAI			4	AAI shall support CRUDQ of ASD-based CNF Resources	AAI	, by leveraging AAI APIs	3.13 AAI shall support CRUDQ of ASD-based CNF Resources Leverage existing AAI APIs Investigate any new AAI APIs for ASD-based CNF Resources (TBD)