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

1. Add VIM from ONAP GUI with VIM location information, tenant authentication information
2. VIM default service url can be configured based on real VIM settings

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

1. All HEAT and 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

1. All VNFs have been onboarded
2. All VNFs images files have been uploaded manually into VIM

1. Use SDC to create core infrastructure service including vDHCP, vAAA, vDNS, and Web server
2. Use SDC to create a service including vBNG
3. Use SDC to create a service including vGMux
4. Use SDC to create a service including vBRG
5. Use SDC to create a service including vG

1. Each service is created successfully and stored in the catalog

1. ONAP platform up and running

1. Use CLAMP Cockpit to create closed loop control for vCPE
2. Distribute the results to policy and DCAE (through SDC)

1. Verify and the policy is distributed to Policy Engine
2. Verify that Blueprint template and meta data (including service UUID, resource UUID, and artifact name) distributed to DCAE inventory

Deploy and activate closed loop control for vCPE

1. Closed loop configuration completed in T203

1. From CLAMP Cockpit, user chooses to deploy vCPE closed loop control

1. DCAE responds by bringing up a VES collector container, loading TCA app to CDAP, and configuring DMaaP to enable data flow from VES collector to TCA.

1. vCPE services have been created
2. Closed loop has been configured

1. ONAP user uses VID to instantiate DHCP, AAA, DNS, and Webserver
2. ONAP user uses VID to instantiate vBNG
3. ONAP user use Robot to instantiate vGMux

1. DHCP, AAA, DNS, and Web Server are up and running
2. vBNG is up and running
3. vGMux is up and running
4. The network connection all the above VNFs are created successfully
5. The closed loop is up and running, DCAE can collect packet loss rate from vGMux and send analytics results to Policy

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

1. ONAP user uses VID to instantiate a vBRG and a VM that is connected to the vBRG
2. Once vBRG is instantiated, its subsequent DHCP request will invoke ONAP to instantiate a vG and complete all required configuration. This step does not require human intervention.
3. ONAP user sign on to the VM connected to the vBRG and test connection to the web server.

1. vBRG and vG are up and running
2. ONAP user can access the web server

1. vCPE service instantiated
2. Customer service instantiated
3. Close loop is up and running

1. Use Robot to invoke vGMux to generate packet loss event
2. The event will trigger self-healing, the process is automatic and does not require human intervention

1. DCAE captures packet loss event and sends event to Policy
2. Policy invokes APPC to restart the vGMux VM
3. vGMux VM is restarted
4. Web server access from customer is disrupted during restarting and restored afterwards

1. vCPE service is created
2. Closed loop is established

1. ONAP user uses Usecase UI GUI to remove vCPE service

1. Closed loop is stopped
2. All vCPE VNFs and VLs are removed
3. DCAE collector container removed and the analytics application unloaded.
4. Closed loop related artifacts (including DCAE template and policy) are removed from ONAP