...
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:
Post Condition:
|
| 1 | ||||||||
| 1 | |||||||||||
| 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:
Post Condition:
|
| 2 | ||||||||
Task:
| 2.1 | |||||||||||
Task:
| 2.2 | |||||||||||
Task:
| 2.3 | |||||||||||
Task:
| 2.4 | |||||||||||
Task:
| 2.5 | |||||||||||
SO CNFM shall process ASD-based CNF Lifecycle orchestration | SO CNFM, ASD Repository, Helm Artifact Repository, OOF, AAI, SDNC Adapter, SDNC, CDS, CNF Adapter | SO CNFM shall process ASD-based CNF Lifecycle orchestration Pre Condition:
Post Condition:
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
| 3.1 | |||||||||||
Create SO CNFM REST API swagger, based on the ASD LCM Restful API, ASD LCM RESTful Protocols for SO CNF Manager and Swagger file (ASD LCM RESTful Protocols for SO CNF Manager) | 3.2 | |||||||||||
Task: Support for SO CNFM NBI API Handler
| 3.3 | |||||||||||
Task:
| 3.4 | |||||||||||
Task:
| 3.5 | |||||||||||
Task:
| 3.6 | |||||||||||
Task:
| 3.7 | |||||||||||
Task: Create SO CNFM Instance Database Management
| 3.8 | |||||||||||
Task:
| 3.9 | |||||||||||
Task:
| 3.10 | |||||||||||
Task:
| 3.11 | |||||||||||
Task:
| 3.12 | |||||||||||
Task:
| 3.13 | |||||||||||
Task:
| 3.14 | |||||||||||
SO Client shall send the A La Carte Request for ASD-based CNF orchestration (note: E2E support is out of PoC scope) | SO Client, SO, SO BPMN, CNFM CNF Adapter | SO Client shall send the A La Carte Request for ASD-based CNF orchestration Pre Condition:
Post Condition:
|
| 4 | ||||||||
Task:
| 4.1 | |||||||||||
Task:
| 4.2? |
...
- The Resource VF(s) in the onboarded Service CSAR will have the following resource main manifest file
- oran_application_name
- oran_application_provider
- oran_release_date_time
- oran_entry_definition_type [ "asd"]
- SO distinguishes the App package based on the "oran_entry_defintion_type" metadata.
- If it is "asd", SO will process the package as the ASD-based CNF.
- SO delegates the ASD-based CNF orchestration to the CNF Manager
...
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
Helm Command Support
- Helm Install
- Helm Uninstall
- Helm Upgrade
Component Communication Security
...
The following sequence diagram depicts design and distribution of ASD service CSAR, based on CNFO. This sequence could be changed.
PlantUML Macro | ||
---|---|---|
| ||
@startuml participant Designer participant Admin participant SDC participant SO_Client participant SO participant CNFM participant CNF_Adapter participant K8S_Plugin participant AAI participant K8S_Cluster autonumber group ASD PACKAGE Distribution hnote over SDC : SDC supports ASD-based Service CSAR Designer -> SDC : Onboarding ASD App Package SDC --> SDC : Onboards ASD App Package and\ngenerates Service CSAR SDC -> SO : Distribute Service CSAR SDC -> AAI : Distribute Service CSAR SDC -> K8S_Cluster : Distribute Service CSAR end group K8S Cluster Admin hnote over Admin : Admin accesses K8S Cluster Admin -> K8S_Cluster : Create/Update/Configure K8S Cluster Admin -> AAI : Add/Register K8S Cluster AAI --> AAI : Add the tenant AAI -> K8S_Plugin : Post Connectivity Info (Kubconfig file) end @enduml |
...