Introduction
The purpose of this article is to describe the vLB use case distribution in Frankfurt Release.
What's new in Frankfurt Release
The Controller Blueprint Archive CBA is a zip archive that hosts all the service model related artifacts (heat templates, blueprints, vtl templates, workflows, etc ... ) that can enable ONAP to assign and instantiate the service.
In Frankfurt release, the cds community introduce the following new functionality:
- CDS Features
- TOSCA Imperative workflow orchestration
- Kafka Message Bus Entry Point blueprint processor Execution
- Resource Lifecycle Management
- CDS Designer UI
- CDS Integration with ONAP Components
- SO component direct integration with CDS via Self Servia API for Meta Data-Driven Orchestration
- Policy component with CDS via Self Servia API for Meta Data Driven Orchestration for all LCM actions.
- Multcloud indirect integration with CDS for CNF instantiation and Post instantiation
The CBA and Data Dictionary are explained in the Modelling Concepts page here: Modeling Concepts
CDS will require a main component to be able to build a service instance, Following the instructions below in the following order to onboard the Data Dictionary and CBA Package.
- Load the latest DD.json and run the dd.sh script in rancher.
- Once this is step is completed, access the CDS UI and upload the latest CBA and execute in the following sequence:
- Enrich
- Save
- Deploy
- if upload via SDC: Click on Download and use the Enriched CBA Package to onboard via SDC Artifact Deployment for the VF Model.
Controller Blueprint Package [Deploy the cba using CDS UI by following the steps of Enrich, Save, Deploy] | Data Dictionary | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
In Frankfurt release, different CBA Package flavors are available to be executed.
NOTE:
| All the data dictionary required to run the vLB E2E Automation and Scale Out use case leveraging CDS is preload in CDS DB: |
After building the CBA and Data Dictionary, we can use the CDS UI to add the Data Dictionary to CDS, and to deploy the CBA in CDS.
First, we logon to CDS UI using the url https://<onap_ip_address>:30497.
Choose Controller Blueprint, select file, and update Metadata, the NEXT.
Controller Blueprint - CBA Package Management Screens
Enrich, Save, Publish, and finally Deploy, and you should receive a success notification.
Resource Definition Screen - Controller Data Dictionary
If we want to add one Dictionary item, we start in the CDS UI home screen, select New Resource.
Paste the Dictionary Definition JSON string and submit.
If we want to add many Dictionary items, we can create a JSON list of all the dictionary items and save them in a file called dd.json, and then run the dd.sh script below in the same folder where dd.json is located.
#!/bin/bash # Author: abdelmuhaimen.seaudi@orange.com # Usage: name this script as dd.sh, and put the data dictionaries list JSON as dd.json in the same directory, and run dd.sh # dd.sh will read the dictionary list JSON from dd.json, will output to stdout the number of Defintions found, and will start pushing them one by one to CDS DB l=`jq '.|length' dd.json` echo "Found $l Dictionary Definition Entries" i=0 while [ $i -lt $l ] do echo "i = $i" d=`jq ".[$i]" dd.json` echo $d #REPLACE <cds-ui> with the IP Address of ONAP curl -k 'https://<cds-ui>:30497/resourcedictionary/save' -v -X POST -H 'Content-type: application/json' -d"$d" sleep 1 echo -e "\n*****************************************\n" i=$(( $i + 1 )) done
Automated Distribution of vLB CDS Service in SDC Model using Robot
The robot script can help the user automate the creation of the VSP and Service model, and also update the resource assignment properties of the service model to run the vLB_CDS blueprint.
To use this feature follow the steps below:
In order to check if the robot is OK, we can check in SDC to check the demoVLB_CDS model exists
Also, we can click on the service model and check the resource assignment properties to ensure that blueprint template name and version are updated.
Manual Distribution of a VNF CBA
Login to ONAP as Designer (cs0008/demo123456!), and click on SDC application.
Part 1 - Create a New Virtual Software Product
In SDC, select the ONBOARD button > click on Create New VSP button > fill in the Name, Vendor, Category , Description and select the Network Package for on-boarding procedure as illustrated below.
Once the forum is populated for New Software Product click on Create.
In Software Product Details Screen in SDC, the users must populate the license information and the software product. For the vLB CDS use case the software product for the heat package is obtain from the following link: vLB CDS HEAT PACKAGE.
Once the for License and Software Product Attachment is populated then click on the Submit button.
Part 2 - Create VF Model and Certify
Click on the Import VSP from the HOME page.
From the list of VSP, select the Specific vLB CDS VSP for IMPORT to create the VF in SDC.
We fill in the VF name and description, etc ..., and click "Create".
Click on "Deployment Artifact", then "Add other arifacts", and select the vDNS.zip CBA.
Check the artifact is uploaded OK, and click on "Certify".
Add a comment, and submit, you should receive a success notification, and we are back in SDC Home Screen.
Part 3 - Create Service Model, Certify and Distribute
Now, let's create a new service model, and add the newly created VF (including CBA artifact) to the new service model. Click on "Add Service"
Add service name and description, and click on "Create". Choose Instantiation Type: Macro.
Click on "Composition", and drag the VF we created from the palette on the left onto the canvas in the middle.
Then, click on "Submit for Testing".
Click on Properties Assignments, then click on the service name, e.g. "CDS-VNF-TEST" from the right bar.
Type "sdnc" in the filter box, and add the sdnc_model_name, sdnc_model_version, and sdnc_artifact_name, and click "Save".
Type "skip" in the filter box, and set "skip post instantiation" to FALSE, then click "Save".
Login as Tester (jm0007/demo123456!) and accept the new service.
Login as Governor (gv0001/demo123456!) and approve for distribution.
Login as Operator (op0001/demo123456!) and click on "Distribute".
Click on "Monitor" to check the progress of the distribution, and check that all ONAP components were notified, and downloaded the artifacts, and deployed OK.
Check SDNC distribution concerning CDS
SDNC to find CDS SDNC database should be now populated with CDS model identification.
kubectl exec -n onap onap-mariadb-galera-mariadb-galera-0 -it -- sh mysql -uroot -psecretpassword -D sdnctl MariaDB [sdnctl]> select sdnc_model_name, sdnc_model_version, sdnc_artifact_name from VF_MODEL WHERE customization_uuid = '88e0e9a7-5bd2-4689-ae9e-7fc167d685a2'; +-----------------+--------------------+--------------------+ | sdnc_model_name | sdnc_model_version | sdnc_artifact_name | +-----------------+--------------------+--------------------+ | test | 1.0.0 | cds-vnf-template | +-----------------+--------------------+--------------------+ 1 row in set (0.00 sec) # Where customization_uuid is the modelCustomizationUuid of the VNf (serviceVnfs response in 2nd postman call from SO Catalog DB)