...
V00010: WAN Resource Onboarding (WAN resource only has properties in template, need to confirm Need to finalize overlay and underlay are seperate VL resources)
| 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 underlay 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 VFC
- Create a new service called VoLTE service and compose it with EPC VNF, IMS VNF and WAN 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 | 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 | 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 |
|
...
