Versions Compared

Key

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

...

  • Core NS instantiation using the Macro flow through NBI Automation.
  • Instantiation, Day0, Day1 and Day2 configuration with help of SO, SDNC, Multicloud (k8s-plugin) and CDS.
  • There are two E2E workflows involved i.e Macro POST (Instantiation) and PUT (Modify Config) operations.

CBA package Download:

Original Upload

https://gerrit.onap.org/r/c/ccsdk/cds/+/113518 (obsolete)

https://gerrit.onap.org/r/gitweb?p=ccsdk/cds.git;a=commit;h=a8fecedef955a594716d96a4c5b5c2564385db1c (obsolete)

Current Repository

https://git.onap.org/ccsdk/cds/tree/components/model-catalog/blueprint-model/service-blueprint/5GC_Simulator_CNF_CDS


Helm Package:


View file
name5G_Core_Helm_package.zip
height250

...

Info
iconfalse

Prerequisites:

  • Update the Verify that SO Mariadb catalogdb table orchestration_flow_reference 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:

VSP:

Image Removed

...

Image Removed

Service:

Instantiation Type = Macro

Image Removed

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

...

NBI Helm Chart Update:

Add the environment variable (which are highlighted in below pic) in below path.

path: oom/kubernetes/nbi/templates/deployment.yaml 

Image Removed

Then, you will need to change also the following parameters :

...

  • in the Service-Macro-Create section and VNF-Macro_modify sections.  (Up to date in Istanbul Release)
  • Verify that SO Mariadb catalogdb service_recipe and northbound_request_ref_lookup are correct.
  • Update k8sregion information in the SO catalogdb and the default version has a duplicate for Region One that should be rationalized.
  • This simulator uses a parameter called snssai which is input at the time of instatniation and can be updated once the service is running. As this is a service level input parameter, it is prefixed by the model name during the assignment of this input as a declared input.  This example and demo use "fiveg" for the default model name, "fiveg" results in an input variable "fiveg0_snssai" being created in the service level when snssai is set to a declared input.  This parameter is specified and used in the definitions and templates of the CBA.  If a model name other than "fiveg" is used, all "fiveg0_snssai" must be changed to "yourmodelnam0.snssai" in the data types and resource definition types in the Definitions folder and the amf, smf, and upf template and mapping files in the Templates folder. 

SDC:

VSP:

Image Added


VF:
Set below properties values at VF level in SDC

Image Added

Service:

Instantiation Type = Macro

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


NBI Updates:

WARNING:  The default override values file supplied with your distribution likely has this entry for nbi.

nbi:
  enabled: false
  config:
    # openstack configuration
    openStackRegion: "Yolo"
    openStackVNFTenantId: "1234"

This entry will cause changes you make to configure NBI to be overwritten when the NBI pod is updated and must be removed.

path: oom/kubernetes/nbi/templates/deployment.yaml 

The default values can remain as is as the values are specified in a values.yaml file.  Prior instructions added k8s config variables but that as of Istanbul is no longer needed.

            - name: ONAP_LCPCLOUDREGIONID
              value: {{ .Values.config.openStackRegion }}
            - name: ONAP_TENANTID
              value: {{ .Values.config.openStackVNFTenantId | quote }}
            - name: ONAP_CLOUDOWNER
              value: {{ .Values.config.cloudOwner }}
            - name: ONAP_K8SCLOUDREGIONID
              value: {{ .Values.config.k8sCloudRegionId }}
            - name: ONAP_K8SCLOUDOWNER
              value: {{ .Values.config.k8sCloudOwner }}


path: oom/kubernetes/nbi/values.yaml

The Values that come with the deployment are as below.

# application configuration
config:
  loglevel: INFO
  logstashServiceName: log-ls
  logstashPort: 5044
  cloudOwner: CloudOwner
  k8sCloudRegionId: k8sregionfour
  k8sCloudOwner: k8scloudowner4
  ecompInstanceId: OOM
  openStackRegion: RegionOne
  openStackVNFTenantId: aaaa

Two of these values (cloudOwner and openStackRegion need to be set to the k8s values;

# application configuration
config:
  loglevel: INFO
  logstashServiceName: log-ls
  logstashPort: 5044
  cloudOwner: k8scloudowner4
  k8sCloudRegionId: k8sregionfour
  k8sCloudOwner: k8scloudowner4
  ecompInstanceId: OOM
  openStackRegion: k8sregionfour
  openStackVNFTenantId: aaaa

Note: This will disable NBI being able to orchestrate in RegionOne on VM's and only deploy CNF's on default k8sregionfour. If you don't use your k8s info and keep openstack options, options, leaving the public_net_id null in your request will default to the openstack values, and if you give it something else, it will use k8s values.

To recap, update the values in the confg section of the NBI values..yaml.

  • openStackRegion = the k8s region
  • cloudOwner = value for k8s cloud owner
  • openStackVNFTenantId = the same tenantid value for

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 |

...