...
| 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 | CMCC OpenLab |
|
| 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 | CMCC OpenLab |
|
| 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 |
CMCC OpenLab
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 |
CMCC OpenLab |
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 |
| Tester Name |
|
- VoLTE VNF onboarding: vendors vEPC and vIMS VNFs are onboarded successfully.
...
