...
V00012: Closed Loop Configuration
Test Case Id | V00012 |
Test Case Name | Closed loop configuration |
Description | This test uses CLAMP to configure closed loop for VoLTE |
Release | Amsterdam |
Preconditions | - DCAE template has been imported (R1 SDC doesn't support DCAE template design)
- Holmes blueprint has been imported
- Holmes correlation rules have been defined
|
Testing Steps | - In CLAMP, choose which VNF and event to monitor
- Bring up CLAMP configuration policy GUI and copy Holmes correlation rules in it
- Bring up CLAMP provisional policy GUI and define reboot provisional policy
- Save the configuration
|
Expected Results | - Closed loop template and blueprint for Holmes are distributed to DCAE
- Configuration policy has been distributed to DCAE
- Provisional policy has been distributed to Policy engine
|
Actual Results |
|
Conclusion (Pass/Fail) |
|
Testing Lab | CMCC OpenLab |
Testing Date |
|
Tester Name |
...
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
|
Actual Results |
|
Conclusion (Pass/Fail) |
|
Testing Lab | CMCC OpenLab |
Testing Date |
|
Tester Name |
|
- Auto-healing for VIM event: DCAE VES collector receives the VNF event from VIM, and forwards it to Holmes. Holmes does the correlation and generates signature event and sends to Policy. Then auto-healing policy is triggered and proper actions are taken to mitigate the situation
- Auto-healing for VNF event: When alarm is generated by VNF, VFC will receive the alarm via vendor’s EMS and forwards to DCAE VES collector. The DCAE collector will then forward alarm to Holmes via DMaaP. Holmes does the alarm correlation and sends signature event to Policy. Finally the auto-healing policy is triggered and proper actions are taken to mitigate the situation
...