Page History

...

• cds-service-mode: 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:

• 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:

...

Notes:

• If the robot script for service model distribution fails, it might be due to a problem in the database, check the JIRA

  Jira
  server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-1400

   for solution, basically we need to increase the size of the database field.

Log into the SO mariadb container.

use catalogdb;

ALTER TABLE vnf_resource_customization
MODIFY IF EXISTS RESOURCE_INPUT varchar(20000);

ALTER TABLE network_resource_customization
MODIFY IF EXISTS RESOURCE_INPUT varchar(20000);

ALTER TABLE allotted_resource_customization
MODIFY IF EXISTS RESOURCE_INPUT varchar(20000);

in so mariadb pod (username/password root/password).

• 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

...