...
- <Postconditions>:
- each POD is a ready Ready status. This ensures that each POD can serve requests.
- Some of the PODs will not reach the Ready status until a day 1 configuration is applied
- The PODs still need verification of containers with a specific ContainerState
PlantUML Macro | ||
---|---|---|
| ||
@startuml participant SO_Client participant SO participant SO_BPMN participant CNFM participant AAI participant SDNC participant OOF participant ASD_Catalog_Mgr participant Helm_Repository participant K8S_Cluster autonumber group ASD-Based CNF Instantiation SO_Client -> SO : Create Service SO -> SO_BPMN : Process and Decompose Service SO_BPMN -> AAI : Create Service Instance opt Service-Level Homing SO_BPMN -> OOF : Homing Information (optional for PoC) OOF -> SO_BPMN : Receive Homing Information (optional for PoC) end SO_BPMN --> SO_BPMN : Process Model Info & Decide flows SO_BPMN -> CNFM : Delegate Resource Orchestration,\npass input parameters CNFM -> ASD_Catalog_Mgr : Get ASD CNFM -> Helm_Repository : Get associated Helm Charts CNFM --> CNFM : Process and decompose ASD and DeploymentItems\n(VF & Vf-Modules) CNFM --> CNFM : get DeploymentItem order and create a sequence list CNFM --> CNFM : execute each deployment item by following the sequence order loop CNFM -> AAI : Create vf-module CNFM -> SDNC : Assign vf-module CNFM --> CNFM : Get AsInstance LifecycleParameterMetadata from the request CNFM --> CNFM : Get the corresponding Helm Chart CNFM --> CNFM : Create a new values file by replacing the values file from the Helm Chart with LifecycleParameterMetadata CNFM --> CNFM : generate K8S resource (e.g., helm template) based on the Helm Chart plus a new custom values file CNFM -> OOF : get a placement decision (for PoC, returns a predefined K8S cluster name) CNFM --> CNFM: set kube config environment for the target K8S Cluster CNFM --> K8S_Cluster : invoke Helm Install with a custom values file CNFM -> AAI : Update vf-module end end @enduml |
...