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: vIMSSvcInst20180606
    2. Select Subscriber Name: Demonstration
      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 
    4. Select Project
      1. This was set via robot.sh init or robot-k8s.sh onap init
    5. Select Owning Entity
      1. This was set via robot.sh init or robot-k8s.sh onap init



  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 Node Instance"
    1. Select "vIMS_Clearwater"
    2. Enter an Instance Name (vIMS20180606 0)
    3. Select product family vIMS
    4. Select LCP Region (this is your openstack node)
    5. Select Tenant
    6. Select Line of Business
      1. This was set by demo init
    7. Select Platform
    8. Click Confirm



  9. Click on Add VF Module 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 SDNC portal and follow the steps about SDNC updates in  Tutorial_vIMS: SDNC Updates
  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 Openstack portal to see what IP's were assigned to bono-0, ellis-0, etc.

2 Comments

  1. Michael O'Brien

    Brian, 

       Hi, good tutorial.  I had a question about section 9 - it looks very similar to the screen scraping done by robot via demo.sh - Ideally there are endpoints that return this data as well that I will look into.

    Tutorial: Creating a Service Instance from a Design Model

    "Click on Add VF but write down the 3 pieces of information highlighted for the SDN Preload"

    /michael

  2. Michael O'Brien

    Brian,

       Hi, I am determining where we can avoid using robot demo.sh and VID for orchestration - and use a pure headless OSS (until R1 is out) - I am info sharing between our 2 tutorials.  It seems that we are able to avoid the VID "Create VF Module" UI - step 13 - it frequently times out (can be ignored) on some environments as the VF VMs come up - I am going to see if I am missing anything (most of the work is in the preload step before).

       Posting to the following works - closed loop TCA/Measurement metrics run OK after after the appc step

    http://{{mso_ip}}:8080/ecomp/mso/infra/serviceInstances/v2/<id>/vnfs/<id>/vfModules

        VID create service instance and add vnf to service instance GUIs are still required

       /michael