Page Comparison

...

For more details on the Clearwater vIMS consult http://clearwater.readthedocs.io

The An example HEAT template plus manifest zip file for uploading to SDC is in gerrit under the demo project (fill in full path) Metaswitch's github (https://github.com/Metaswitch/clearwater-onap) .

You will need to modify the nested yaml files.

Unzip the file and change the lines that refernence "server" to be the component name "_server" in two places.

So for bono.yaml change sever to bono_sever in both the resource and in the output.

bono.yaml: bono_server:

bono.yaml: value: { get_attr: [ bono_server, accessIPv4 ] }
dns.yaml: dns_server:
dns.yaml: value: { get_attr: [ dns_server, accessIPv4 ] }
ellis.yaml: ellis_server:
ellis.yaml: value: { get_attr: [ ellis_server, accessIPv4 ] }
homer.yaml: homer_server:
homer.yaml: value: { get_attr: [ homer_server, accessIPv4 ] }
homestead.yaml: homestead_server:
homestead.yaml: value: { get_attr: [ homestead_server, accessIPv4 ] }
ralf.yaml: ralf_server:
ralf.yaml: value: { get_attr: [ ralf_server, accessIPv4 ] }
sprout.yaml: sprout_server:
sprout.yaml: value: { get_attr: [ sprout_server, accessIPv4 ] }

Also remove COPYING from the zip file since that isnt in the manifest.json.

Recreate the zip with a command like: zip clearwater.20180606.zip *

High Level Steps

1. SDC: Onboard the infrastructure service (using SDC portal)
2. AAI : Create cloud account (using AAI API)
3. VID : start to Instantiate the VNF (using VID portal)
4. SDNC : declare VNF Profile (using SDNC admin portal) and preload VNF data (using SDNC API)
5. VID : finalize VNF instanciation (usind VID portal)
6. Install and run clearwater automated  test suite
7. VID: Delete VNF instance

...

1. Login to the Portal with the service designer account (cs0008)
   1. http://portal.api.simpledemo.openecomp.org:8989/ECOMPPORTAL/login.htm
      
2. Select the SDC Application from the portal home
3. Re-use an existing Licence  (TBD to do vIMS specific license)
   
4. Select ONBOARD from the top menu
5. Hover over the Add button and select "New Vendor Software Product"
6. Fill in the diaglog box as below. 
   
   1. Name: vIMS_Clearwater
   2. Vendor: Select from list based on license being used
   3. Category: Infrastructure (Generic)
   4. Description: vIMS from Clearwater
      
      
      
      
      
7. Click SAVE
8. Select the yellow icon under the License Agreement 
   
   
   
   
9. Select the License Information (Feature Group appears after you pick a License Agreement)
   1. License Version: 1.0
   2. License Agreement: select from list
   3. Feature Group: Select from list
      
      
      
      
      
10. Save by clicking on the disk icon on the upper right hand side 
    
    
    
    
11. Create or download the Create  ZIP file to your desktop
    1.  You can either create the zip file from the heat data out of the gerrit repository on your client or 
    2. download the zip file from the wiki clearwater-v0.1.zipFrom the  zip file or files from https://github.com/Metaswitch/clearwater-onap with the modifications to the yaml files described above.
       
       
12. Select the "Overview" menu item on the left hand side
    
    
    
13. Click on the "Select file" box to upload
    
    
    
    
    
14. Select the ZIP file for the Clearwater VNF from your desktop
    
    
    
    
15. SDC will analyze the ZIP file and display the heat templates with validation status
    
    
    
    
16. Click on Check In to save your work (and this makes the Submit button active)
17. Click on Submit (you should get a dialog box saying it succeeded)
18. Next, we need to return to the SDC home screen to create a new virtual function (VF) based on the virtual software product (VSP) we just created.
    1.  Hover over the arrow to the right of "Onboard" in the bread crumb trail; a menu will appear. Select "Home".
19.  Click on the  "Vendor Software Product Repository" icon in the upper right corner of the SDC "Home" screen. 
    
    
    
    
20. In the dialog box that pops up use the Search box to filter for vIMS
    
    
    
    
21. Select the vIMS_Clearwater and click on the arrow to display the VSP Description row
22. Select the "Import VSF" icon on the right side (its the left one with the up arrow)
23. Select "Create" on the upper right hand corner to create the VSF which may take some time
    
    
    
    
24. It should display success and now we can use the left hand menu items
25. Select ICON and then click on a desired ICON (I picked the purple one)
    
    
26. Click on "Deployment Artifact" to generate/update and display the deployment configurations.
    
    
    
27. The "Information Artifact" page can be used to attach a variety of different data and metadata to the VF.
    
    1. We dont need to do anything on this page - just click on the menu item
28. The "TOSCA Artifacts" page shows the TOSCA orchestration information generated by SDC from the VF's specifications.
    
    1. We dont need to do anything on this page - just click on the menu item
29. Data properties can be added to the VF on the "Properties" page.
    
    1. We dont need to do anything on this page - just click on the menu item
30. Clicking on left pane "Composition" under "Properties" takes us into the actual Design Studio, where a graphical representation of our underlying VSP is shown on the canvas. To return to the VF specification, click on "VF: vIMS_Clearwater" in the bread crumbs above the canvas.
    
    1. Note that there is no internal networking in the current heat template so the servers dont seem to be connected. 
    2. They are all on the internet and that connection is not shown
       
       
       
       
31. The "Activity Log" page tracks all changes to the VF.
    1. We dont need to do anything on this page - just click on the menu item
32. The "Deployment" page shows the resources related to the deployment of the VF, and a variety of information can be inspected from here.
    
    1. We dont need to do anything on this page - just click on the menu item
       
33. Finally, the "Inputs" page show the parameters used to set up the VF. Details can be viewed by clicking on the various disclosure arrows.
    1. We dont need to do anything on this page - just click on the menu item
       
34. At this point, our new VF needs to be submitted for testing as part of the ONAP workflow. Do not check in the VF at this point, simply click on "Submit For Testing".
35. A form will appear, prompting you for a message to the test team. Enter one and click "Save".
36. You will be returned to the SDC Home screen, where our VF now shows as being "Ready for testing". You may need to filter for vIMS if there are a lot of robot test runs on your home page.
    
    
    
37. Test the Virtual Function (VF)
    1. Logout and Login as the tester account (jm0007) 
    2. Select SDC application
    3. Select the vIMS icon
    4. Click on Start Testing
    5. Click on Accept
    6. Fill in the message to the designer with some text
38. Logout and Login as the service designer (cs0008) and go back to SDC application
39. Filter for vIMS if you need to and see the vIMS is certified
    
    
    
    
40. Hover over the "Add" panel, and click the "Add Service" button when it appears.
41. Fill in the parameters
    1. Name: vIMS_Clearwater_Service
    2. Description: vIMS_Clearwater_Service
    3. Category:  Mobility
       1. you could select voip call control as the other pertinent choice
    4. Project Code: 11111
       1. this is a text only attribute that is used for tracking what project owned a VNF/Service. Its not used by ONAP.
    5. Click Create
       
       
       
       
42. As when we created our virtual function, the sidebar links were greyed; now that the service has been created, they're active. Click on the icon link, and select an icon for the service.
43. Next, click on "Composition". This is the step at which we actually "design" the service we'll be distributing. Initially, the "Composition" page shows an empty canvas and a couple of default network elements. Enter IMS in the search window . 
44. Now we can see our vIMS VF in the sidebar. Drag the VF out of the sidebar and drop it onto the canvas.
    
    
    
45. You have now created a new service consisting of the single virtual function. Before it can be distributed for use, though, the service must be tested and approved. Click "Submit for testing" and enter a message in the dialog which appears. Click "Save".
46. You'll be returned to the SDC Home screen, and an alert showing that the new service has been successfully submitted for testing will appear. Note that both our virtual function and our new service now appear on the SDC Home screen; the service shows "v0.1" and a status of "Ready for testing".
47. jm008: This completes our Designer's involvement in the workflow, and the service now goes to the Tester for testing and approval. Log out and log back in as jm0007. Click on "SDC" to access the SDC Home page. Note that it's once again no longer empty: the "tutorial service" artifact has been added to our workflow.
    
    1. select vIMS icon
    2. Submit for Testing
    3. Accept
    4. Enter message
    5. Log out
48. gv001: Log in as gv0001. 
    1. Access the SDC Home page, 
    2. Click on "waiting for approval" 
    3. The now tested and accepted service appears with version "1.0" and the status "Waiting for distribution".
       
       
       
    4. Click on the service artifact to access its details and then click the "Approve" button above the form
       
    5. Enter text for the message
49. op0001: The Governor's part in the workflow is now complete, and it only remains for a user in the "Ops" role to actually distribute the service. Log out, and log in again as op0001. Access the SDC Home page, which now shows the "tutorial service" with a status of "Distribution Approved".
    
    1. select the vIMS Service
    2. click on Distribute
    3. Enter text
       
       
       
       
       
       
       
       
       
       
    4. Click on Monitor to see that artifacts are distributed correctly (use refresh button inside the app next to the application search box not in the browser)
       
       
       
       
50. The model is now ready for use by VID to instantiation but we need to setup the rest of the environment

...