Tutorial: Creating a Service Instance from a Design Model

Known Issues

https://jira.onap.org/browse/UCA-22

UCA-17 - Getting issue details... STATUS

UCA-19 - Getting issue details... STATUS

6589635

Creating a Service Instance

In this tutorial we show how to take a service design that has been distributed and create a running instance of the service. 

Notice the service you created in VID

To simplify this we are going to use scripts (with some selenium robot scripts) to create the design, pre-load customer and network information, and orchestrate parts of the virtual firewall closed loop example.  The following steps assume that you have completed and understand basic concepts from the setting up the platform and using the portal tutorials. 

Let's start by finding the IP Address of vm1-robot in the Rackspace list of servers.  Use this vm1-robot IP address, your Rackspace private key, and the PuTTY client to login to vm1-robot as root.

Note: The current default LCP Region is IAD - to use DFW switch the example zip in the last section - currently though we have hardcoding that must be fixed:  DOC-6 - Getting issue details... STATUS

At the command prompt type

Wait for all steps to complete (will take 60-120 sec) as shown below

If you want to see the details of what ran, you can open report.html in a browser. (located within openecompete_container docker container)

From the ONAP portal, login to the VID application using demo user, browse to locate the demo SDC Service Models, and Deploy an instance of the service you created - not the pre-populated demoVFW.

(Note: deploy your "service" above - not demoVFW or demoVLB - these 2 are leftover pre-population artifacts of the init script and will be removed)

Fill in the information (Instance Name=DemoInstance, Demonstration, vFW) for a Service Instance as shown below and press Confirm.

Wait for a response and close the window

You should now see a service instance displayed.

Add a VNF using the drop down button, complete, and enter the following information.   The tenant and LCP region drop down choices may be different for your Rackspace account.  Both IAD and DFW support heat templates - but currently only IAD is supported in this demo until  DOC-6 - Getting issue details... STATUS

Wait for and close the response window.

Return to the PuTTY window and type the command to load VNF configuration information

DO NOT Navigate from the Deploy page before adding the VF Module below - or you will need to search for it - then hit edit

     
    ./demo.sh preload <vnf_name> <module_name>
    example
    ./demo.sh preload DemoVNF DemoModule

Wait for the results as shown below

Add a VF Module using the drop down button.

Fill in information for the VF module (service name = Service) and confirm.

Watch as the 3 VMs for the VF start to come up on Rackspace (dialog is still up)

Create VF Module hangs - vFW VMs are created

Eventually you will see a (red-herring) poll timeout - we need to adjust the wait time and # of retries here - anyway the 3 VM's are up (with pings but not necessarily with 200 health checks on the processes)

see  UCA-19 - Getting issue details... STATUS

Select close, and later cancel (for now) - as the VMs are actually up 

For now cancel the Create VF Module dialog (the VMs were created)

Browse our new vFW service

Wait for the response and close the window as was done in prior steps.    The VF Module creation can also be viewed as a stack in Rackspace as shown below.

To complete the service instance we will run one more script that mounts the Traffic Generator on the Application Controller to enable policy driven configuration changes.   Return to the PuTTY window, type the command and wait for the response as shown below.

     ./demo.sh appc DemoModule

see the vFW sink page - to view traffic generation stats

We are currently having issues with the traffic generator - both starting the stream and also actually sshing to the VM (looks like the ssh key in the env is not picked up)

Fix: the repo URL in the vFW zip has changed to 

  #repo_url: https://ecomp-nexus:8443/repository/raw/org.openecomp.simpledemo

  repo_url: https://nexus.onap.org/content/sites/raw/org.openecomp.demo/vnfs/vfw/1.0.0-SNAPSHOT

Also the private key for the 3 vFW VM's is in /testsuite/robot/assets/keys/robot_ssh_private_key.pvt

Note: the overrides in the env are not picked up for the network/IPs as well - these are the sample py defaults - a JIRA is open

UCA-17 - Getting issue details... STATUS

The platform and virtual function interactions in the control loop are summarized here.

Error Handling

Handle MSO Failure on RAM Quota exceeded

A default rackspace account is only allocated 128G but we will require 

      "requestState": "FAILED",
      "statusMessage": "Received vfModuleException from VnfAdapter: category='INTERNAL' message='Exception during create VF 0 : Stack error (CREATE_FAILED): 

Resource CREATE failed: Forbidden: resources.vsn_0: Quota exceeded for ram: 

Requested 4096, but already used 130048 of 131072 ram (HTTP 403) (Request-ID: req-02439f0a-c8a4-4fe7-8d79-d6fa99bd4f57) - stack successfully deleted' rolledBack='true'",
      "percentProgress": 100,
      "finishTime": "Tue, 23 May 2017 22:19:11 GMT"

Handle MSO Failure on Create VF Module

Update: 20170523: looks like the template defaults are not being modified - and pass through

UCA-17 - Getting issue details... STATUS

This type of MSO failure means the demo VNF was retried with the same defaults - a retry will just fail on another IP conflict for the port.

The openstack tenant also happens to have other instances of the VNF that look like they are causing a port resource contention - clean/reset your VM's for now.

05/18/17 15:05:57 HTTP Status: OK (200)
{
  "request": {
    "requestId": "6c0afeaf-42a4-4628-9312-2305e533f673",
    "startTime": "Wed, 17 May 2017 19:04:56 GMT",
    "requestScope": "vfModule",
    "requestType": "createInstance",
...
    "requestStatus": {
      "requestState": "FAILED",
      "statusMessage": "Received vfModuleException from VnfAdapter: category='INTERNAL' message='Exception during create VF 0 : Stack error (CREATE_FAILED): Resource CREATE failed: IpAddressInUseClient: resources.vsn_private_1_port: 

Unable to complete operation for network 6dfab28d-183e-4ffd-8747-b360aa41b078. The IP address 10.1.0.13 is in use. - stack successfully deleted' rolledBack='true'",
      "percentProgress": 100,
      "finishTime": "Wed, 17 May 2017 19:05:48 GMT"
    }
  }
}