...
V00013: VoLTE Service Instantiation (WAN service should be independent of VoLTE and instantiated separately, need to discuss)
| Test Case Id | V00013 |
| Test Case Name | VoLTE Service Instantiation |
| Description | This test covers the whole VoLTE service instantiation process |
| Release | Amsterdam |
| Preconditions | - VoLTE service has been created, V00011 has passed
- Closed loop has been configured, V00012 has passed
- PEs have been configured and integrated with corresponding SDN WAN controller
- DC GWs have been configured and integrated with corresponding SDN local controller
|
| Testing Steps | - ONAP user uses Usecase UI GUI to start VoLTE service instantiation
- Usecase UI will guide the user to deploy each of vEPC VNFs. User needs to choose data center location and fill in input parameters defined in TOSCA template
- Usecase UI will guide the user to deploy each of vIMS VNFs. User needs to choose data center location and fill in input parameters defined in TOSCA template
- Usecase UI will guide the user to deploy WAN service. User needs to choose PEs and DC GWs, fill in WAN underlay and overlay parameters
|
| Expected Results | - vEPC service is instantiated successfully, including all vEPC VNFs and VLs
- vIMS service is instantiated successfully, including all vIMS VNFs and VLs
- WAN service is instantiated successfully, including underlay and overlay networks
- Holmes analytics container is brought up correctly by DCAE
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
V00014: VoLTE Auto-healing
| Test Case Id | V00014 |
| Test Case Name | VoLTE Auto |
...
| -healing |
| Description | This test covers the closed loop with alarm correlation and auto-healing |
| Release | Amsterdam |
| Preconditions | - VoLTE closed loop has been configured
- VoLTE service has been instantiated
- SPGW VNF supports event generation
- VNF guest OS supports event generation
- MultiVIM supports event collection from guest OS and event forwarding
|
| Testing Steps | - Use Robot test script to shutdown standby MPU VM inside SPGW VNF
|
| Expected Results | - EMS collects standby MPU offline event from SPGW VNF and sends the event to VFC
- MultiVIM doesn't receive heartbeat event from standby MPU guest OS for a period of time and triggers alarm which is sent to DCAE VES collector
- Holmes receives MPU offline events
- Holmes receives MPU guest OS heartbeat missing events
- Holmes does correlation of the two types of events and generate one signature event and sends it to Policy
- Policy triggers provisional policy and reboot action is sent to VFC
- VFC uses VNFM driver to reboot standby MPU VM
- Standby MPU is reboot
- Clear event is sent from SPGW VNF about standby MPU back online
- Heartbeat from standby MPU VM is received by MultiVIM and clear event is sent by MultiVIM about heartbeat recovery
- Holmes does the event correlation and sends Clear signature event to Policy
- Policy stops the reboot action
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
- Service termination: When user terminates the VoLTE service, VNFs and related resource for the service are properly removed, and WAN connectivity between the two data center is also removed successfully.