Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. POST: Instantiation,Day0 and Day1 (will update the snssai value in CNF while creation/Instantiation) will perform.
  2. PUT: Day2 can perform (will update the snssai value for Modify Config flow).


Description:


This guide explains to realize the 5G Slicing CNF instantiation of dummy AMF, SMF and UPF network components as PODs in the k8s cluster and applying slicing configurations via ConfigMap k8s resource.

The following pre-requisites are required on ONAP Frankfurt instance to execute the usecase.

· Dummy Helm Charts to instantiate AMF, SMF & UPF

  • CBA package
  • NBI – NBI image 7.0.2
  • SO – SO image 1.7.1
  • Multicloud/K8splugin – Multicloud image latest


Helm artifacts for AMF, SMF & UPF:

  1. Instantiation, day0 & day1
    1.  Base helm package amf_cloudtech_k8s_charts.tgz for instantiation contains following resources.
Info
iconfalse

AMF package:

amf/

amf/Chart.yaml

amf/values.yaml

amf/templates/

amf/templates/configmap.yaml

amf/templates/deployment.yaml

  

                 b. Profile artifact template-profile.tar.gz contains the following resources.

Info
iconfalse

Profile package:

manifest.yaml

override_values.yaml


profile artifact carries snssai parameters for the day0 slice configurations inside override_values.yaml

Day2:

Config templates for each AMF, SMF & UPF instances as helm package for the day2 configurations contains the following resources. For instance the amf config template amf-config-template.tar.gz for AMF instance contains following resources


Info
iconfalse

AMF Config Template :

amf/

amf/Chart.yaml

amf/values.yaml

amf/templates/

amf/templates/configmap.yaml

Config template helm package will be placed inside CBA package along the side profile artifact.

The day2 config-templates will be modified from the Kotlin script before uploaded to multicloud with the ConfigMap name already instantiated. This is to ensure that config-template would update the same ConfigMap which is existing already.


CBA package impacts:

The following new workflows introduced in the CBA along with the existing workflow “resource-assignment” compare to firewall CNF usecase from the Frankfurt.

  1. Instantiation, Day0 & Day1
    • resource-assignment
                This CDS workflow executes kotlin script K8sProfileUpload.kt – responsible to upload profile artifact.
    • config-assign
    • config-deploy
                This CDS workflow executes kotlin script DayOneConfig.kt – responsible to update the config-template with appropriate(instantiated configmap) ConfigMap name and upload it using K8splugin config template API. This is being invoked
      from SO POST api.
  2. Day2
    1. config-assign-day-2
    2. config-deploy-day-2

                     This CDS workflow executes kotlin script KotlinK8sUpdateConfig.kt – responsible to execute K8splugin Values API for day2 configurations. This is being invoked from SO PUT api.

Design time activities:

POST Operation Process:

In SDC vf Design --> create a property as "snssai" and declare it as input in Properties Assignment section, Even in service design refer that same VF and declare it as input.

...

Info
iconfalse

Prerequisites:

  • Update the SO catalogdb table as below for config-assign and config-deploy process from SO to CDS
  • Update the CBA package with VF name, i.e we need to create the "snssai" property at VF level (ex: VF name "fiveg" and property is "snssai"), so it will look in Service as "fiveg0_snssai".

SDC:

Set below properties values at VF level in SDC

Image Added


Set below properties values at Service level in SDC

  • Set “skip_post_instantiation_configuration = false” in SDC to enable post
  • controller_actor = CDS
  • Add cba package details in sdnc properties
    • sdnc_artifact_name
    • sdnc_model_name
    • sdnc_model_version


Image Added


SO Maria DB:

Code Block
languagesql
firstline1
titleorchestration_flow_reference
collapsetrue
MariaDB [catalogdb]> select * from  orchestration_flow_reference;

| 429 | Service-Macro-Create | 1 | AssignServiceInstanceBB | 1 | 102 | NULL | NULL |
| 432 | Service-Macro-Create | 2 | CreateNetworkCollectionBB | 1 | 102 | NULL | NULL |
| 435 | Service-Macro-Create | 3 | AssignNetworkBB | 1 | 102 | NULL | NULL |
| 438 | Service-Macro-Create | 4 | AssignVnfBB | 1 | 102 | NULL | NULL |
| 441 | Service-Macro-Create | 5 | AssignVolumeGroupBB | 1 | 102 | NULL | NULL |
| 444 | Service-Macro-Create | 6 | AssignVfModuleBB | 1 | 102 | NULL | NULL |
| 447 | Service-Macro-Create | 7 | ControllerExecutionBB | 1 | 102 | vnf | config-assign |
| 450 | Service-Macro-Create | 8 | AssignPnfBB | 1 | 102 | NULL | NULL |
| 453 | Service-Macro-Create | 9 | WaitForPnfReadyBB | 1 | 102 | NULL | NULL |
| 456 | Service-Macro-Create | 10 | ActivatePnfBB | 1 | 102 | NULL | NULL |
| 459 | Service-Macro-Create | 11 | CreateNetworkBB | 1 | 102 | NULL | NULL |
| 462 | Service-Macro-Create | 12 | ActivateNetworkBB | 1 | 102 | NULL | NULL |
| 465 | Service-Macro-Create | 15 | CreateVolumeGroupBB | 1 | 102 | NULL | NULL |
| 468 | Service-Macro-Create | 16 | ActivateVolumeGroupBB | 1 | 102 | NULL | NULL |
| 471 | Service-Macro-Create | 17 | CreateVfModuleBB | 1 | 102 | NULL | NULL |
| 474 | Service-Macro-Create | 18 | ActivateVfModuleBB | 1 | 102 | NULL | NULL |
| 477 | Service-Macro-Create | 19 | ControllerExecutionBB | 1 | 102 | vnf | config-deploy |
| 480 | Service-Macro-Create | 20 | ActivateVnfBB | 1 | 102 | NULL | NULL |
| 483 | Service-Macro-Create | 21 | ActivateNetworkCollectionBB | 1 | 102 | NULL | NULL |
| 486 | Service-Macro-Create | 22 | ActivateServiceInstanceBB | 1 | 102 | NULL | NULL |

...