...
V00001: WindRiver OpenStack VIM Resource OnboardingRegistration
| Test Case Id | V00001 |
| Test Case Name | WindRiver OpenStack VIM Resource OnboardingRegistration |
| Description | WindRiver OpenStack VIM Resource OnboardingRegistration |
| 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 registered successfully
- Tenant authentication information is stored successfullycorrectly
|
| 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 OnboardingRegistration
| Test Case Id | V00003 |
| Test Case Name | VMWare OpenStack VIM Resource OnboardingRegistration |
| Description | VMWare OpenStack VIM Resource OnboardingRegistration |
| 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
|
| 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
|
| Expected Results | - VIM resource is onboarded registered successfully
- Tenant authentication information is stored successfully
| Actual Results | Conclusion (Pass/Fail) | Testing Lab | Tester Name |
V00004: VMWare OpenStack 2nd VIM Resource Onboarding
- correctly
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab |
|
| Tester Name |
|
...
V00005: Data Center Gateway Controller Resource OnboardingRegistration
| Test Case Id | V00005 |
| Test Case Name | Data Center Gateway Controller Resource OnboardingRegistration |
| 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 Register each DC gateway local controller from ONAP GUI (need to confirm which ONAP GUI supports SDN local controller - OOM or UsecaseUI?) ESR GUI with the needed information (location, IP, port, authentication information, etc)
|
| Expected Results | - The DC local controller is onboarded registered successfully
- The DC local controller information is stored successfullycorrectly
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Tester Name |
|
V00006: SDN WAN PE Controller Resource OnboardingRegistration
| Test Case Id | V00006 |
| Test Case Name | SDN WAN PE Controller Resource OnboardingRegistration |
| 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 Register SDN WAN controller from ONAP GUI (need to confirm which ONAP GUI supports SDN local controller - OOM or UsecaseUI?) ESR GUI with the needed information (IP, port, authentication information, etc)
|
| Expected Results | - The SDN WAN controller is onboarded registered successfully
- SDN WAN controller information is stored correctly
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | CMCC OpenLab |
| Tester Name |
|
...
| 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 the following vEPC VNFD csar files one by one:
- vSPGW
- vEPDG
- vPCRF
- vHSS
- vMME
- Use SDC to onboard the following vIMS VNFD csar files one by one:
- vPCSCF
- vI/SCSCF
- vTAS
|
| 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 |
|
...
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 |
|
...
V00015: VoLTE Service Termination
| Test Case Id | V00015 |
| 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 | - 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 networks
- Closed loop is stopped
- 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 |
|