Page Comparison

...

1. Login into portal as demo
2. Select Browse SDC Service Models
3. Filter on IMS
4. Clickon Deploy for your vIMS service
5. Fill in the Create Service Instance
   1. Instance Name: vIMSClearwaterService1
   2. Select Subscriber Name: Demonstration3 
      1. this is in the drop down from the query to AAI and we set that name in the POSTMAN PUT to AAI in the previous section
   3. Select Service Type: vIMS
      1. This is from the same update to AAI we did for Demonstration 3.
      
      
6. Click Confirm to create the Service Instance
   
   
   
   
   
7. Close the window and the View/Edit Service Instance Pane will appear
   
   
   
   
   
8. Click on "Add VNF"
   1. Select "vIMS_Clearwater"
   2. 
      
      
9. Click on Add VF but write down the 3 pieces of information highlighted for the SDN Preload. The Service Instance ID is the one that is going to be unique to your environment. Generic-vnf-type and vnf-type should be the same if you are following this tutorial.
   1. Service Instance Id: 1e736900-db02-4bd2-9e7b-72ac1a08c3f7  
      1. This can be selected and copy/pasted into a text file
   2. Generic-vnf-type: "vIMS_Clearwater 1"
      1. This is the string after the "/" in the VNF TYPE row.
   3. vnf-type: VimsClearwater..base_clearwater..module-0
      
      
      
      
10. Pick a name for the VF like "vIMSVNFTEST1" that you will be using for the next step.
11. Go to the SDNC Preload section portal and upload the preload-topology data using preload-topology-clearwater.json as your template with the updates from the tutorial.After createing the VF profile and VF Preload data in SDNCfollow the steps about SDNC updates in  Tutorial_vIMS: Create AAI cloud account
12. then go ahead with the following steps in the VID
13. Click on the VmsClearwater..bas..clearwater..module-0 to bring up the VF Create Dialog.
    1. You may want to uncheck the rollback box since the default SO timeout will not be sufficient 
       
       
       
       
14. Since there are only public IPs being used you will have to go to the RACKSPACE portal to see what IP's were assigned to bono-0, ellis-0, etc.