...
- 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.
- 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:
...
- 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:
...
- If instantiation fails, and complains about the naming service not available, check that the SDN 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.
