Category: VNF Onboarding and Service Creation
vCPE VNFs Onboarding
| Test Case ID | T201 |
| Test Case Name | vCPE VNFs Onboarding |
| Description | Onboard vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG |
| Actual Results | All VNFs onboarded successfully with Robot script (TODO: add screenshot) |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab, Integration-SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
vCPE Service Creation
| Test Case ID | T202 |
| Test Case Name | vCPE Service Creation |
| Description | This creates vCPE service |
| Actual Results | All service created and distributed successfully (TODO: screenshot) |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab, Integration-SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
Closed Loop Configuration
| Test Case ID | T203 |
| Test Case Name | Closed loop configuration |
| Description | Create and distribute closed loop artifacts from CLAMP |
| Actual Results | Policy is preset. No need to design in this use case |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab, Integration-SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
Closed Loop Deployment
| Test Case ID | T204 |
| Test Case Name | Closed loop deployment |
| Description | Deploy and activate closed loop control for vCPE |
| Actual Results | Closed loop is preset in DCAE with ONAP install, and policy is installed with a preinstalled script (see details in Use Case service design wiki) |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab, Integration-SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
Category: Service Instantiation and Monitoring
Infrastructure Service Instantiation
| Test Case ID | T301 |
| Test Case Name | vCPE Infrastructure Service Instantiation |
| Description | This test covers the infrastructure service instantiation process, including DHCP, AAA, DNS, Webserver, vBNG, and vGMux. |
| Actual Results | All networks and VNF were successfully instantiated (TODO: screenshot) |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
Customer Service Instantiation
| Test Case ID | T302 |
| Test Case Name | vCPE Customer Service Instantiation |
| Description | This test covers the customer service instantiation process, including vBRG emulator and vG and the related configuration. |
| Actual Results | Customer service successfully instantiated and configured. Need to manually update temp_network_heat_template and network_resource tables to set aic_version_max = 3.0 |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
Category: Closed Loop
vCPE Auto-healing
| Test Case ID | T401 |
| Test Case Name | vCPE Auto-healing |
| Description | This test covers the closed loop to restart vGMux when packet loss is detected. |
| Actual Results | Closed loop test succeeded. Was able to restart vGMUX VM at the expected event. Need to manually insert identity-url for CloudRegion in A&AI TODO: Screenshot of vgmux reboot |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
Category: Service Termination
vCPE Service Termination
| Test Case ID | T501 |
| Test Case Name | vCPE Service Termination |
| Description | This test covers vCPE service termination process |
| Actual Results | Succeeded in removing all components of the customer service with Openstack operation and script TODO: screenshot of stack and network after deletion |
| Conclusion (Pass/Fail) | Pass |
| Testing Lab | WindRiver Lab SB-03 |
| Testing Date | Nov. 26, 2018 |
| Tester Name | Yang and Brian |
Reference
ONAP Beijing: Understanding the vFWCL use-case mechanism
...
Configuring SNIRO Emulator for vCPE Testing
...
Issues fixed during integration test
Set up ONAP and health check
| Number | Issues | JIRA | Workaround | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | SDNC fails health check intermittently |
| Reduce replica from 3 to 1 and not using clustering make the problem go away | ||||||||
2 | SDC GUI doesn't come up |
| The workaround is find an old working image for sdc-frontend and replace the failing one | ||||||||
| 3 | SO fails on health check due to bpmn can't start |
| Find a older working bpmn image from nexus3 repo and replace image version in Helm deployment with kubectl edit command | ||||||||
| 4 | Portal GUI doesn't work on 8989 port | Use Firefox with portal 30225, and when switching to SDC click on the info icon at the url bar and accept unsecure access to SDC GUI | |||||||||
| 5 | All health check failed, due to the connection failure in k8s. All cluster nodes are in Ready state: root@oom-rancher:~/oom/kubernetes/robot# kubectl -n onap get node | Restart oom-orch node can make k8s correction problem go away. You may have to restart a few pod manually like aaf-locate and aaf-service. But ONAP data seems preserved. |
VNF onboarding, service creation and distribution
...