Page History

...

• Updated slice information on the ConfigMap and inside pod supportedNsssai inside ConfigMap:

Image Added

• Inside the AMF, SMF & UPF pods the slice details updated in the following location like below.

Image Added

PUT Operation Process:

...

Modify-Config flow of slice (Day-2):

Process: 

1. SO triggers PUT request for day2 configuration.
2. SO triggers config-assign-day-2 workflow of CDS. CDS executes the workflow.
3. SO triggers config-deploy-day-2 workflow of CDS. CDS processes config-deploy-day-2 workflow. The workflow would execute kotlin script KotlinK8sUpdateConfig.kt. The script performs the following activities in sequence. Steps from b) to c) will be executed for all the vf-modules except base.
   1. Script invokes A&AI and fetch vf-modules details
   2. Resolve snssai array
   3. Execute Config Values API of K8splugin by passing

Notes:
     Kotlin processing of snssai array from

SO PUT request SO PUT api would apply slice configurations on AMF, SMF and UPF instances. The PUT request carries the slice details which further been updated on the k8s cluster on the configmap.
The following json structure represents the configurations received from SO PUT for a VFModule.
The sNssai array would be resolved from the CBA to make it available to Kotlin

Image Added

• Kotlin invocation of values api of K8splugin 
• The following configuration api from the multicloud/k8splugin would be invoked to process configurations. It takes configuration template as input in the payload which essentially contains helm package that carries configurations like
  ConfigMap in this case.

POST https://<IP>:30283/api/multicloud-k8s/v1/v1/rb/definition/<rbname>/<rb-version>/profile/<profile-name>/config

Image Added

• Updated slice information on the ConfigMap and inside pod
       supportedNsssai inside ConfigMap:

Image Added

Inside the AMF, SMF & UPF pods the slice details updated in the following location like below.

Image Added