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 (WAN resource only has properties in template, need to confirm overlay and underlay are seperate 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 onboard create a VL resource and upload WAN underlay network CSAR file. Make sure controllerInfo property is set to SDNC in the template
- In SDC onboard 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 | V00011 |
| Test Case Name | VoLTE Service Creation |
| Description | This test creates VoLTE service. To workaround SDC limitation on nested service support, in R1 we create separate dummy VNFs in VoLTE service, and link those VNFs to vEPC, vIMS and WAN services |
| Release | Amsterdam |
| Preconditions | - vEPC service has been created
- vIMS service has been created
- WAN service has been createdunderlay and overlay resources have been onboarded
- All required ONAP artifacts (DG, DCAE template, Holmes blueprint, SO workflow, etc) have been designed and uploaded to corresponding components
|
| Testing Steps | - In SDC onboard a dummy VNF, called EPC, which links its property nsServiceInvariantUUID to vEPC service using ID property invariantUUID. Set the VNF controllerInfo property to VFC
- Onboard a dummy VNF, called IMS, which links its property nsServiceInvariantUUID to vIMS service using ID property invariantUUID. Set the VNF controllerInfo property to VFCOnboard the dummy VNF, called WAN, which links to WAN service using ID property. Set the VNF controllerInfo property to SDNC
- Create a new service called VoLTE service and compose it with EPC VNF, IMS VNF and WAN dummy VNFs
- Upload DG artifact in SDC
- Upload DCAE template
- Upload SO workflow
- underlay and overlay VL resources
- Test, certify and approve VoLTE service
- Distribute VoLTE service
|
| Expected Results | - VoLTE service is created successfully
- VoLTE service is stored in catalog
- Service Creation event is sent via DMaaP
- Other modules (SO, VID, Usecase UI, CLAMP, VID, etc) receives the event
- VoLTE service is CSAR file can be retrieved from SDC catalog by other modules using SDC API
|
| 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?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 | V00013 |
| Test Case Name | VoLTE Service Instantiation |
| Description | This test covers the whole VoLTE service instantiation process |
| Release | Amsterdam |
| Preconditions | - All external systems (VIM, SDN WAN controller, SDN local controller, vendors SVNFM and EMS) have registered with ESR
- 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
- EVPN VXLAN tunnel has been set up manually between edge and core DC gateway. At this moment, underlay network between PEs has not been set up yet, so EVPN and VXLAN tunnel is configured but may not be working, but it's ok.
- Install a web server in core data center
|
| Testing Steps | - ONAP user uses logins Usecase UI GUI to start VoLTE service instantiation
- Usecase UI will guide the user to deploy vEPC VNFs. User needs to choose data center location for each VNF and fill in input parameters defined in TOSCA template
- Usecase UI will guide the user to deploy vIMS VNFs. User needs to choose data center location for each VNF and fill in input parameters defined in TOSCA template
- or verify all needed parameters for vEPC, vIMS, WAN underlay and overlay
- User will click a button to deploy VoLTE serviceUsecase UI will guide the user to deploy WAN service. User needs to input necessary PEs and DC GWs info, 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
- Client UE can access network through mobile network, e.g. access the web server
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
...
| 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 | - Use Robot test script to 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
| Test Case Id | V00016 |
| Test Case Name | VoLTE Service Termination |
| Description | This test covers VoLTE service termination process |
| Release | Amsterdam |
| Preconditions | - VoLTE service has been created
- Closed loop has been configured and started
- 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 remove VoLTE service
|
| Expected Results | - Closed loop is stopped
- vEPC service is removed successfully, including all vEPC VNFs and VLs
- vIMS service is removed successfully, including all vIMS VNFs and VLs
- WAN service is removed successfully, including underlay and overlay networksnetwork setup
- Holmes analytics container is removed by DCAE
- Closed loop related artifacts (including DCAE template, configurational policy and provisional policy, DG, workflows) are removed from ONAP
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
...
