Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Introduction

The purpose of this article is to describe the vDNS use case distribution in Dublin Release.

What's new

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. 

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.

Distribution of a VNF CBA

Part 1 - Create VF Model and Certify

Login to ONAP as Designer (cs0008/demo123456!), and click on SDC application.


Using a sample CBA vDNS.zip, we start by adding a VF in SDC.


We fill in the service 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 2 - Create Service Model, Certify and Distribute

Now, let's create a new service model, and add the VF to the new service model. Click on "Add Service"


Add service name and description, and click on "Create"


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".


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.




  • No labels