There are two tasks to complete before we can use VID to instantiate the vIMS VNF.
- We need to indicate in AAI what account the vIMS service is support it and in which cloud location
- After we create the service instance via VID , we need to set the preload data for the vIMS VNFs in SDNC
For the AAI updates we would use "demo.sh init" to populate AAI with the data for the "Demonstration" customer.
Here we will use POSTMAN to PUT the object for a Demonstration3 customer.
Note that you will have to put your tenantid into the string :
<YOUR_TENANT_HERE>
Note that we are setting up this account for vFW, vDNS and vIMS so we can use the tenant for more things.
Using POSTMAN to update AAI requires headers and basic authorization shown.
{ "global-customer-id": "Demonstration3", "subscriber-name": "Demonstration3", "subscriber-type": "INFRA", "service-subscriptions": { "service-subscription": [ { "service-type": "vFW", "relationship-list": { "relationship": [{ "related-to": "tenant", "relationship-data": [ {"relationship-key": "cloud-region.cloud-owner", "relationship-value": "Rackspace"}, {"relationship-key": "cloud-region.cloud-region-id", "relationship-value": "IAD"}, {"relationship-key": "tenant.tenant-id", "relationship-value": "<YOUR_TENANT_HERE>"} ] }] } }, { "service-type": "vLB", "relationship-list": { "relationship": [{ "related-to": "tenant", "relationship-data": [ {"relationship-key": "cloud-region.cloud-owner", "relationship-value": "Rackspace"}, {"relationship-key": "cloud-region.cloud-region-id", "relationship-value": "IAD"}, {"relationship-key": "tenant.tenant-id", "relationship-value": "<YOUR_TENANT_HERE>"} ] }] } }, { "service-type": "vIMS", "relationship-list": { "relationship": [{ "related-to": "tenant", "relationship-data": [ {"relationship-key": "cloud-region.cloud-owner", "relationship-value": "Rackspace"}, {"relationship-key": "cloud-region.cloud-region-id", "relationship-value": "IAD"}, {"relationship-key": "tenant.tenant-id", "relationship-value": "<YOUR_TENANT_HERE>"} ] }] } } ]} }
You should get back a 201 Created response code and be able to see the data in AAI via the matching GET (/aai/v8/business/customers/customer/Demonstration3)
Need to have 5 parameters to set SDNC Preload (vnf-name and vnf-type are the critical ones)
generic-vnf-type":"vIMSSWProduct_test 1",
"service-type":"c8cba5cc-b4cd-4903-9f9a-80b50255d18b", (UPDATE_THIS_ONE)
"vnf-name":"vIMSVNFTEST1",
"vnf-type":"VimsswproductTest..base_clearwater..module-0" (CHECK_THIS_ONE)
"generic-vnf-name":"vIMSVNFTEST1",
SDNC Updates
SDNC Admin Portal
- Access the admin portal on <sdnc_ip>:8843/login.htm
- Login
- Click on VNF
- Fill in the VNF Profile
- VNF Type: VimsClearwater..base..clearwater..module-0
- Available Zone Count: 100
- Equipment Role: vIMS
- click Submit
- Should seed green box: Successfully added VNF Profile
- Go to the SDNC VNF-API section next
SDNC VNF-API
- Access <sdnc_ip>:8282/apidoc/explorer/index.html on the SDNC VM
- Click on VNF-API
- Scroll down to the POST /operations/VNF-API/preload-vnf-topology-operation
- Paste the preload-vnf-topology-clearwater.json data into the input box
- make sure to edit the values for "pub_key" and "service-type":
- {"vnf-parameter-name":"pub_key","vnf-parameter-value":"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDQXYJYYi3/OUZXUiCYWdtc7K0m5C0dJKVxPG0eI8EWZrEHYdfYe6WoTSDJCww+1qlBSpA5ac/Ba4Wn9vh+lR1vtUKkyIC/nrYb90ReUd385Glkgzrfh5HdR5y5S2cL/Frh86lAn9r6b3iWTJD8wBwXFyoe1S2nMTOIuG4RPNvfmyCTYVh8XTCCE8HPvh3xv2r4egawG1P4Q4UDwk+hDBXThY2KS8M5/8EMyxHV0ImpLbpYCTBA6KYDIRtqmgS6iKyy8v2D1aSY5mc9J0T5t9S2Gv+VZQNWQDDKNFnxqYaAo1uEoq/i1q63XC5AD3ckXb2VT6dp23BQMdDfbHyUWfJN imported-openssh-key"},
"generic-vnf-type":"vIMSSWProduct_test 1",
"service-type":"c8cba5cc-b4cd-4903-9f9a-80b50255d18b",
"vnf-name":"vIMSVNFTEST1",
"vnf-type":"VimsClearwater..base..clearwater..module-0"
"generic-vnf-name":"vIMSVNFTEST1",
- make sure to edit the values for "pub_key" and "service-type":
Click on Submit