1. The WindRiver OpenStack VIM is configured with tenant information and provider networks
2. The WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
3. Create flavor onap.hpa.flavor1 and aggregate
   

    $ openstack aggregate create --property aggregate_instance_extra_specs:sriov_nic=sriov-nic-intel-1234-5678-physnet1:1 aggr11

    $ openstack flavor create onap.hpa.flavor1 --id auto --ram 512 --disk 40 --vcpus 4

    $ openstack flavor set onap.hpa.flavor1 --property aggregate_instance_extra_specs:sriov_nic=sriov-nic-intel-1234-5678-physnet1:1

Use CLI command to add the above info.

# Create complex
$ oclip complex-create \
-j <street2> -r <physical_location> -x <complex_name> \
-y <data_center_code> -lt <latitude> -l <region> \
-i <street1> -lo <longitude> -S <state> \
-la <lata> -g <city> -w <postal-code> \
-z <complex_name> -k <country> -o <elevation> \
-q <identity_url> -m <aai_url> -u <aai_username> -p <aai_password>

# Create cloud
$ oclip cloud-create -e <esr-system-info-id> -b <user-name> -I <cloud-region>
\
-x <cloud-owner> -y <cloud-region> -j <password> \

-w <cloud-region-version> -l <default-tenant> -url <service-url> \
-n <complex_name> -q <cloud-type> -r <owner-defined-type> \
-Q <system-type> -i <identity-url> -g <cloud-zone> \
-z <ssl-insecure> -k <system-status> -c <cloud-domain> \
-m <aai_url> -u <aai_username> -p <aai_password>

# Associate Cloud with complex

oclip complex-associate -x <complex_name> -y <cloud-region> -z <cloud-owner> -m <aai_url> -u <aai_username> -p <aai_password>

# Register Cloud with Multicloud

$ oclip multicloud-register-cloud -x <cloud-region> -y <cloud-owner> -m http://<ip>:<port> 

1. VIM is registered successfully
2. Tenant authentication information is stored correctly

1. Use CLI command to add the above info.

1. VIM is registered successfully
2. Tenant authentication information is stored correctly

1. All TOSCA templates are ready
2. VNF license has been created

1. Use SDC to import, test and certify the following VNF templates, including both yaml and env files: vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG

1. All VNFs are onboarded successfully

All VNFs have been boarded

Service creation successfully

1. All VNFs have been boarded
2. Service has been created

We can see Service and VNF in UUI portal

Use CLI command

Service is created successfully and stored in the catalog

1. vCPE services have been created
2. vCPE infrastructure service has been instantiated

1. Use CLI command

1. vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG are up and running
2. ONAP user can access the web server

vCPE service is created

1. Use CLI command

1. All vCPE VNFs and VLs are removed