V00001: WindRiver OpenStack VIM Resource Onboarding
| Test Case Id | V00001 |
| Test Case Name | WindRiver OpenStack VIM Resource Onboarding |
| Description | WindRiver OpenStack VIM Resource Onboarding |
| Release |
|
| Preconditions | - The WindRiver OpenStack VIM is configured with tenant information and provider networks
- The WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
|
| Testing Steps | - Add VIM from ONAP GUI with VIM location information, tenant authentication information
- VIM default service url can be configured based on real VIM settings
|
| Expected Results | - VIM resource is onboarded successfully
- Tenant authentication information is stored successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab |
|
| Tester Name |
|
V00002: WindRiver OpenStack 2nd VIM Resource Onboarding
| Test Case Id | V00002 |
| Test Case Name | WindRiver OpenStack 2nd VIM Resource Onboarding |
| Description | This is to test multi VIM support |
| Release |
|
| Preconditions | - The first WindRiver OpenStack VIM has been successfully onboarded
- A new WindRiver OpenStack VIM is configured with tenant information and provider networks
- The new WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
|
| Testing Steps | - Add the new VIM from ONAP GUI with VIM location information, tenant authentication information
- The new VIM default service url can be configured based on the new VIM settings
|
| Expected Results | - The new VIM resource is onboarded successfully
- The new VIM Tenant authentication information is stored successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab |
|
| Tester Name |
|
V00003: VMWare OpenStack VIM Resource Onboarding
| Test Case Id | V00003 |
| Test Case Name | VMWare OpenStack VIM Resource Onboarding |
| Description | VMWare OpenStack VIM Resource Onboarding |
| Release |
|
| Preconditions | - The VMWare OpenStack VIM is configured with tenant information and provider networks
- The VMWare OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
|
| Testing Steps | - Add VIM from ONAP GUI with VIM location information, tenant authentication information
- VIM default service url can be configured based on real VIM settings
|
| Expected Results | - VIM resource is onboarded successfully
- Tenant authentication information is stored successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab |
|
| Tester Name |
|
V00004: VMWare OpenStack 2nd VIM Resource Onboarding
| Test Case Id | V00004 |
| Test Case Name | VMWare OpenStack 2nd VIM Resource Onboarding |
| Description | This is to test multi VIM support |
| Release |
|
| Preconditions | - The first VMWare OpenStack VIM has been successfully onboarded
- A new WindRiver OpenStack VIM is configured with tenant information and provider networks
- The new WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
|
| Testing Steps | - Add the new VIM from ONAP GUI with VIM location information, tenant authentication information
- The new VIM default service url can be configured based on the new VIM settings
|
| Expected Results | - The new VIM resource is onboarded successfully
- The new VIM Tenant authentication information is stored successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab |
|
| Tester Name |
|
V00005: Data Center Gateway Resource Onboarding
| Test Case Id | V00005 |
| Test Case Name | Data Center Gateway Resource Onboarding |
| Description | This is part of WAN setup testing. Each data center has its own gateway and controlled by local SDN controller |
| Release | Amsterdam |
| Preconditions | - VIMs from the same vendor have been successfully onboarded
- Each DC gateway has been manually installed and configured correctly
- Each DC gateway local controller has been manually installed and configured correctly
|
| Testing Steps | - Onboard each DC gateway local controller from ONAP GUI (need to confirm which ONAP GUI supports SDN local controller - OOM or UsecaseUI?) with the needed information (IP, port, authentication information, etc)
|
| Expected Results | - The DC local controller is onboarded successfully
- The DC local controller information is stored successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Tester Name |
|
V00006: WAN PE Resource Onboarding
| Test Case Id | V00006 |
| Test Case Name | WAN PE Resource Onboarding |
| Description | This is part of WAN setup testing. There are at least two PEs in the network, controlled by one SDN WAN controller |
| Release | Amsterdam |
| Preconditions | - Each PE router has been manually installed and configured correctly
- SDN WAN controller has been manually installed and configured correctly
|
| Testing Steps | - Onboard SDN WAN controller from ONAP GUI (need to confirm which ONAP GUI supports SDN local controller - OOM or UsecaseUI?) with the needed information (IP, port, authentication information, etc)
|
| Expected Results | - The SDN WAN controller is onboarded successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Tester Name |
|
V00007: VoLTE VNFs Onboarding
| Test Case Id | V00007 |
| Test Case Name | VoLTE VNFs Onboarding |
| Description | VNFD csar files need to be onboarded one by one |
| Release | Amsterdam |
| Preconditions | - All vEPC and vIMS VNFD csar files can pass VNFSDK checking
|
| Testing Steps | - Use SDC to onboard vEPC VNFD csar files one by one
- Use SDC to onboard vIMS VNFD csar files one by one
|
| Expected Results | - vEPC csar files are onboarded successfully
- vIMS csar files are onboarded successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
V00008: vEPC Service Creation
| Test Case Id | V00008 |
| Test Case Name | vEPC Service Creation |
| Description | This creates vEPC service |
| Release | Amsterdam |
| Preconditions | - All vEPC VNFD csar files can pass VNFSDK checking
- All VNFs images files have been uploaded manually into ONAP
|
| Testing Steps | - Use SDC to create vEPC service with the following VNFs
- vSPGW
- vEPDG
- vPCRF
- vHSS
- vMME
- As part of vEPC service composition, create Virtual Links (VL) to connect the VNFs together according to vEPC service design
|
| Expected Results | - vEPC service is created successfully
- vnfmInfo is correctly pointed to vendor's VNFM
- vEPC service is successfully stored in catalog
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
V00009: vIMS Service Creation
| Test Case Id | V00009 |
| Test Case Name | vIMS Service Creation |
| Description | This test creates vIMS service which includes VNFs and Network Service |
| Release | Amsterdam |
| Preconditions | - All vIMS VNFs csar files can pass VNFSDK checking
- All VNFs images files have been uploaded manually into ONAP
|
| Testing Steps | - In SDC create vIMS service with the following VNFs
- vPCSCF
- vI/SCSCF
- vTAS
- As part of vIMS service composition, create Virtual Links (VL) to connect the VNFs together according to vIMS service design
|
| Expected Results | - vIMS service is created successfully
- vnfmInfo is correctly pointed to vendor's VNFM
- vIMS service is successfully stored in catalog
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
V00010: WAN Service Creation
| Test Case Id | V00010 |
| Test Case Name | WAN Service Creation |
| Description | This test creates WAN service |
| Release | Amsterdam |
| Preconditions | - All PNFs (PE, DC gateway) resources have been onboarded
- All required network connection types (VLAN, MPLS L3 VPN, VXLAN, etc) are defined by SDC
|
| Testing Steps | - In SDC create WAN service
- In service composition, pull in 2 PEs
- In service composition, pull in 2 data center gateways
- Create underlay network as following:
- DC GW1 → PE1 as vlan
- DC GW2 → PE2 as vlan
- PE1 → PE2 as MPLS L3 VPN
- Create overlay network DC GW1 → DC GW2 as VXLAN
|
| Expected Results | - Underlay WAN network created successfully
- Overlay WAN network create successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
V00011: VoLTE Service Creation
| 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 created
- All required ONAP artifacts (DG, DCAE template, Holmes blueprint, SO workflow, etc) have been designed
|
| Testing Steps | - In SDC onboard the dummy VNF, called EPC, which links to vEPC service using ID property. Set the VNF controllerInfo to VFC
- Onboard the dummy VNF, called IMS, which links to vIMS service using ID property. Set the VNF controllerInfo to VFC
- Onboard the dummy VNF, called WAN, which links to WAN service using ID property. Set the VNF controllerInfo to SDNC
- Compose VoLTE service with EPC, IMS and WAN dummy VNFs
- Upload DG artifact in SDC
- Upload DCAE template
- Upload SO workflow
- Test 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 retrieved from SDC catalog by other modules
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Testing Date |
|
| Tester Name |
|
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
- 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.