Test Results @CMCC lab
Image Added
Category: External System Registration
V00001: WindRiver OpenStack VIM Registration
...
| Test Case Id | V00006 |
| Test Case Name | Vendors' EMSs Registration |
| Description | Register all VNF vendors' EMSs |
| Release | Amsterdam |
| Preconditions | - All VNF vendor's EMS have been installed and configured
|
| Testing Steps | - Register all vendors' EMSs using ONAP ESR GUI with the needed information (IP, port, authentication information, etc)
|
| Expected Results | - All EMSs are registered successfully with ONAP
- All EMSs information is stored correctly in ONAP
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Tester Name |
|
Category: VNF Onboarding and Service Creation
V00007: VoLTE VNFs Onboarding
...
V00010: WAN Resource Onboarding (Need to finalize overlay and underlay are seperate VL resourcesUnderlay and Overlay templates are preloaded into SDC, this test case can be removed if not needed anymore)
| Test Case Id | V00010 |
| Test Case Name | WAN Resource Onboarding |
| Description | This test onboards WAN resource using SDC |
| Release | Amsterdam |
| Preconditions | - WAN underlay network template (.yaml) has been defined and packaged in a CSAR file
- WAN overlay network template (.yaml) has been defined and packaged in a CSAR file
|
| Testing Steps | - In SDC create a VL resource and upload WAN underlay network CSAR file. Make sure controllerInfo property is set to SDNC in the template
- In SDC create a VL resource and upload WAN overlay network CSAR file. Make sure controllerInfo property is set to SDNC
|
| Expected Results | - WAN underlay network resource onboarded successfully and shown in catalog
- WAN overlay network resource onboarded successfully and shown in catalog
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
...
| Test Case Id | V00012 |
| Test Case Name | Closed loop configuration |
| Description | This test uses CLAMP to configure closed loop for VoLTE. There are 4 configurations: - Provisional rules for Policy
- Correlation rules for Holmes
- Holmes microservice Blueprint for DCAE
- VES configuration ?(in R1, there is no configuration needed)
|
| 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 VNF SPGW and events (VNF Fault and VM Fault) to monitor
- Bring up CLAMP configuration policy GUI and copy Holmes correlation rules in it
- Bring up CLAMP provisional policy GUI and define healing 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 |
|
Category: Service Instantiation and Monitoring
V00013: VoLTE Service Instantiation
...
| Test Case Id | V00014 |
| Test Case Name | System Performance and Alarm Monitoring |
| Description | This test uses Usecase UI GUI to monitor system performance and event |
| Release | Amsterdam |
| Preconditions | - VoLTE service has been instantiated
- Closed loop for VoLTE has been configured and started
|
| Testing Steps | - ONAP user uses Usecase UI GUI to check system performance, such as CPU, memory and disk usage
- ONAP user views the VNF alarms collected by ONAP
|
| Expected Results | - System performance (including system CPU, memory and disk usage) is shown on ONAP Usecase UI GUI
- VNF alarms, specified in CLAMP for the closed loop, are shown in Usecase UI GUI
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
Category: Closed Loop
V00015: VoLTE Auto-healing
| Test Case Id | V00015 |
| Test Case Name | VoLTE Auto-healing |
| Description | This test covers the closed loop with alarm correlation and auto-healing |
| Release | Amsterdam |
| Preconditions | - VoLTE service has been instantiated
- VoLTE closed loop has been configured and started
- SPGW VNF supports event generation
- VNF guest OS supports event generation
- MultiVIM supports event collection from guest OS and event forwarding
|
| Testing Steps | - Manually shutdown standby MPU VM inside SPGW VNF. This should trigger the VNF and VIM to generate alarms
|
| 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 healing action is sent to VFC
- VFC uses SVNFM driver to heal standby MPU VM
- Standby MPU is healed
- 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 healing action
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
Category: Service Termination
V00016: VoLTE Service Termination
...