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 Integration with ONAP Components
- SO ControllerExeuctionBB allows the ONAP operator to execute any action into CDS for a given scope of vnf, vfmodule, and pnf.
- Policy CDS Actor support allows the ONAP operator to executor any action into CDS for a given scope of vnf, vfmodule and pnf.
- Additional Details click on the link: CDS actor support in Policy
Deck of Cards | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deck of Cards | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NOTE:
dd El Alto cds ui with source-db.zip | 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.
Card |
Within the E2E automation provided by CDS, we have a capability that can generate a name for a component, like a VNF or VF Module. This capability runs with ONAP POLICY component, where POLICY has the rule that will be used to generate the names The override.yaml file above has an option "preload=true", that will tell the POLICY component to run the push_policies.sh script as the POLICY PAP pod starts up, which will in turn create the Naming Policy and push it. To check that the naming policy is created and pushed OK, we can run the commands below.
In case the policy is missing, we can manually create and push the SDNC Naming policy using the commands below.
Card |
IntroductionThe purpose of this article is to describe the vLB use case distribution in El Alto Release. What's new in El AltoThe 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. Controller Design Studio CDS should receive a notification when a new service model is distributed by SDC, and then CDS will download the CBA CSAR file and deploy it. In El Alto, distribution of the vLB CDS Service model can now be automated using a Robot Script. Automated Distribution of vLB CDS Service in SDC Model using RobotThe 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 CBALogin to ONAP as Designer (cs0008/demo123456!), and click on SDC application. Part 1 - Create a New Virtual Software ProductIn 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 CertifyClick 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 DistributeNow, 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_version, 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.
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 CBALogin to ONAP as Designer (cs0008/demo123456!), and click on SDC application. Part 1 - Create a New Virtual Software ProductIn 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 CertifyClick 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 DistributeNow, 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 "con" in the filter box, and set "skip post instantiation" to FALSE and controller_actor to "CDS" then click "Save". Distribute the service model once the service is certified. 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 CDSSDNC to find CDS SDNC database should be now populated with CDS model identification.
|