Video Demo for vFW CDS Casablanca

Owned by A. Seaudi
Last updated: May 06, 2019 by Yuriy Malakov
25 min read

Introduction:

This video shows the vFW use case being instantiated on Casablanca.

What's new:

We can see from the demo that now we don't need to perform SDNC Preloading to instantiate the service. The VNF naming and IP addressing will be auto assigned.

 

Video Demo of the vFW instantiation:

Summary of the video demo:

Create A&AI Customer by executing below script: 

Robot Script Command
./demo-k8s.sh onap init

 

Distributing the vFW service model using the robot script.

Robot Script Command
./demo-k8s.sh onap distributeVFWNG

 

Then, we can use a Postman collection that has 3 Rest Calls and some code to automate the instantiation of the vFW use case:

 

 

 

 

  • 1st Rest call will give us the service model details like UUID, Invariant UUID, and Service Model Name.

 

  • 2nd Rest call will give us the VNF and VF Module details.

STEP CDS2: Expose SO Catalog API

SO Catalog DB is NOT exposed by default, you will need something like the command below to be able to send the CDS #2 rest call to SO Catalog and get back the service VNF model details.

kubectl -n onap expose pod onap-so-so-catalog-db-adapter-56d9cc554b-9fszd --type=LoadBalancer

 

 

  • 3rd Rest call will pull the details from the 1st and 2nd calls, and build the SO Service Assignment and Activation request.

  • I added a 4th Rest call in the collection that will pull the request id from the 3rd call coming from SO, and will show us the status of the requets, so we can track the progress, and see if it completes successfully.

Environment preparation for the Postman Collection:

In order to run the Postman collection correctly, we need to create 3 environment variables in Postman:

  • cds-service-model: This is the name of the service model distributed by the robot script, you can find it by running CDS #1 call once and looking for the VNF that has today's date and time.

    • cds-instance-name: This is the name of the service instance we will instantiate.

  • k8s: This is our ONAP Load Balancer IP Address.

Also, we need to update our IaaS Openstack parameters in the body of the SO Service Instantiation Rest call CDS#3:

  • lcpCloudRegionId : the cloud-region name 

  • tenantId : the tenant id

  • public_net_id : the public network id in Openstack

  • onap_private_net_id : the private network id in Openstack, we need this as this is not created by the auto assignment service

  • onap_private_subnet_id : and the private subnet id

  • pub_key : the public key to be put on the VMs

  • image_name : Ubuntu 14 image name

  • flavor_name : flavor

  • sec_group : security group that will be applied to the VMs

 

 

Results of the Postman Rest calls:

You can find below the output of the calls shown in the video:

Setup A&AI Customer first by execution below robot script: 

 

Output of the robot script to distribute the vFW service model

 

Output of CDS #1 - SDC Service Catalog

 

Output of CDS #2 - SO Service VNFs

 

Output of CDS #3 - SO Service Assign & Activate

 

Output of CDS #4 - SO Active Infra Requests

 

Postman Collection:

Notes:

 

  • If instantiation fails, and complains about the naming service not available, check that the SDNC Naming policies are active. You can check by policy API or go to POLICY from PORTAL and check the 3 Naming policies shown in the screenshot below exist.