1. The WindRiver OpenStack VIM is configured with tenant information and provider networks
2. The WindRiver OpenStack VIM services (console, auth, neutron, image, etc) are accessible from ONAP by IP

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

Use CLI command to add the above info. 

$ oclip vnfm-create -b <name> -c <type> -e <vendor> -v <version> -g <url> -x <vim-id> -y <vnfm-id> -i <user-name> -j <user-password> -q <vnfm-version> -m <aai_url> -u <aai_username> -p <aai_password>

1. VNFM is registered successfully
2. The URL is stored correctly

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

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

All VNFs are onboarded successfully

All VNFs have been boarded

Service creation successfully

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

1. All the VNFs has been certified on SDC successfully

1. Use UUI to onboard all the VNFs 

All VNFs are onboarded successfully, created successfully and stored in the etsicatalog

1. All the VNFs has been onboarded successfully

1. Use UUI to onboard all the service which is distributed on SDC

Service is onboarded successfully, created successfully and stored in the etsicatalog

Onboard VNF and service in UUI portal successfully

Use CLI command or use UUI portal instantiate service

Service is created successfully and stored in the nslcm

1. vCPE services have been created

1. Use CLI command or use UUI portal instantiate service

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

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

1. Shut off the vgmux vm via OpenStack
2. Use UUI portal to heal the vm

vgmux vm restard successfully

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

1. Use CLI command or use UUI portal instantiate service

All vCPE VNFs and VLs are removed

vCPE service is created and terminated

1. Use CLI command or use UUI portal instantiate service

All vCPE service is removed