-
Story
-
Resolution: Done
-
Medium
-
None
-
None
SO CNFM shall process ASD-based CNF Lifecycle orchestration
Pre Condition:
- ASD and App onboarding packages are stored in the Catalog Registry
- Helm Chart(s) are stored in the Helm Artifact Registry
- Image(s) are stored in the Image Registry
- Target K8S Cluster(s) are ready
- Cloud-Region and Tenants are defined in AAI
- AAI shall support CRUDQ of ASD-based CNF Resources
-
- Leverage existing AAI APIs
- Leverage AAI K8S Resource schema which was defined for CNFO
- Take a look at the CNFO logic how to interface with AAI
- Investigate any new AAI APIs for ASD-based CNF Resources (future consideration)
Post Condition:
- ASD-based CNF is provisioned by SO CNFM
Note: in the initial PoC, ASD external CPDs parameters for the primary network will be used (e.g., loadbalancerIP, externalIPs) to configure the K8s service or ingress controller that the ExtCpd represents
Note: ASD Registry, Helm Artifact Registry, Image Artifact Registry will be handled by another Epic, which is defined in Application Package Distribution