Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »


V00001: WindRiver OpenStack VIM Resource Registration

Test Case IdV00001
Test Case NameWindRiver OpenStack VIM Resource Registration
DescriptionWindRiver OpenStack VIM Resource Registration
Release
Preconditions
  1. The WindRiver OpenStack VIM is configured with tenant information and provider networks
  2. The WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
Testing Steps
  1. Add VIM from ONAP GUI with VIM location information, tenant authentication information
  2. VIM default service url can be configured based on real VIM settings
Expected Results
  1. VIM resource is registered successfully
  2. Tenant authentication information is stored correctly
Actual Results
Conclusion (Pass/Fail)
Testing Lab
Tester Name


V00003: VMWare OpenStack VIM Resource Registration

Test Case IdV00003
Test Case NameVMWare OpenStack VIM Resource Registration
DescriptionVMWare OpenStack VIM Resource Registration
Release
Preconditions
  1. The VMWare OpenStack VIM is configured with tenant information and provider networks
  2. The VMWare OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
Testing Steps
  1. Add VIM from ONAP GUI with VIM location information, tenant authentication information
  2. VIM default service url can be configured based on real VIM settings
Expected Results
  1. VIM resource is registered successfully
  2. Tenant authentication information is stored correctly
Actual Results
Conclusion (Pass/Fail)
Testing Lab
Tester Name


V00005: Data Center Gateway Controller Resource Registration

Test Case IdV00005
Test Case NameData Center Gateway Controller Resource Registration
DescriptionThis is part of WAN setup testing. Each data center has its own gateway and controlled by local SDN controller
ReleaseAmsterdam
Preconditions
  1. Each DC gateway has been manually installed and configured correctly
  2. Each DC gateway local controller has been manually installed and configured correctly
Testing Steps
  1. Register each DC gateway local controller from ONAP ESR GUI with the needed information (location, IP, port, authentication information, etc)
Expected Results
  1. The DC local controller is registered successfully
  2. The DC local controller information is stored correctly
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Tester Name


V00006: SDN WAN Controller Resource Registration

Test Case IdV00006
Test Case NameSDN WAN Controller Resource Registration
DescriptionThis is part of WAN setup testing. There are at least two PEs in the network, controlled by one SDN WAN controller
ReleaseAmsterdam
Preconditions
  1. Each PE router has been manually installed and configured correctly
  2. SDN WAN controller has been manually installed and configured correctly
Testing Steps
  1. Register SDN WAN controller from ONAP ESR GUI with the needed information (IP, port, authentication information, etc)
Expected Results
  1. The SDN WAN controller is registered successfully
  2. SDN WAN controller information is stored correctly
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Tester Name


V00007: VoLTE VNFs Onboarding

Test Case IdV00007
Test Case NameVoLTE VNFs Onboarding
DescriptionVNFD csar files need to be onboarded one by one
ReleaseAmsterdam
Preconditions
  1. All vEPC and vIMS VNFD csar files can pass VNFSDK checking
Testing Steps
  1. Use SDC to onboard the following vEPC VNFD csar files one by one:
    1. vSPGW
    2. vEPDG
    3. vPCRF
    4. vHSS
    5. vMME
  2. Use SDC to onboard the following vIMS VNFD csar files one by one:
    1. vPCSCF
    2. vI/SCSCF
    3. vTAS
Expected Results
  1. vEPC csar files are onboarded successfully
  2. vIMS csar files are onboarded successfully
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00008: vEPC Service Creation

Test Case IdV00008
Test Case NamevEPC Service Creation
DescriptionThis creates vEPC service
ReleaseAmsterdam
Preconditions
  1. All vEPC VNFD csar files can pass VNFSDK checking
  2. All VNFs images files have been uploaded manually into ONAP
Testing Steps
  1. Use SDC to create vEPC service with the following VNFs
    1. vSPGW
    2. vEPDG
    3. vPCRF
    4. vHSS
    5. vMME
  2. As part of vEPC service composition, create Virtual Links (VL) to connect the VNFs together according to vEPC service design
Expected Results
  1. vEPC service is created successfully
  2. vnfmInfo is correctly pointed to vendor's VNFM
  3. vEPC service is successfully stored in catalog
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00009: vIMS Service Creation

Test Case IdV00009
Test Case NamevIMS Service Creation
DescriptionThis test creates vIMS service which includes VNFs and Network Service
ReleaseAmsterdam
Preconditions
  1. All vIMS VNFs csar files can pass VNFSDK checking
  2. All VNFs images files have been uploaded manually into ONAP
Testing Steps
  1. In SDC create vIMS service with the following VNFs
    1. vPCSCF
    2. vI/SCSCF
    3. vTAS
  2. As part of vIMS service composition, create Virtual Links (VL) to connect the VNFs together according to vIMS service design
Expected Results
  1. vIMS service is created successfully
  2. vnfmInfo is correctly pointed to vendor's VNFM
  3. vIMS service is successfully stored in catalog
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00010: WAN Service Creation

Test Case IdV00010
Test Case NameWAN Service Creation
DescriptionThis test creates WAN service
ReleaseAmsterdam
Preconditions
  1. All PNFs (PE, DC gateway) resources have been onboarded
  2. All required network connection types (VLAN, MPLS L3 VPN, VXLAN, etc) are defined by SDC
Testing Steps
  1. In SDC create WAN service
  2. In service composition, pull in 2 PEs
  3. In service composition, pull in 2 data center gateways
  4. Create underlay network as following:
    1. DC GW1 → PE1 as vlan
    2. DC GW2 → PE2 as vlan
    3. PE1 → PE2 as MPLS L3 VPN
  5. Create overlay network DC GW1 → DC GW2 as VXLAN
Expected Results
  1. Underlay WAN network created successfully
  2. Overlay WAN network create successfully
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00011: VoLTE Service Creation

Test Case IdV00011
Test Case NameVoLTE Service Creation
DescriptionThis 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
ReleaseAmsterdam
Preconditions
  1. vEPC service has been created
  2. vIMS service has been created
  3. WAN service has been created
  4. All required ONAP artifacts (DG, DCAE template, Holmes blueprint, SO workflow, etc) have been designed
Testing Steps
  1. In SDC onboard the dummy VNF, called EPC, which links to vEPC service using ID property. Set the VNF controllerInfo to VFC
  2. Onboard the dummy VNF, called IMS, which links to vIMS service using ID property. Set the VNF controllerInfo to VFC
  3. Onboard the dummy VNF, called WAN, which links to WAN service using ID property. Set the VNF controllerInfo to SDNC
  4. Compose VoLTE service with EPC, IMS and WAN dummy VNFs
  5. Upload DG artifact in SDC
  6. Upload DCAE template
  7. Upload SO workflow
  8. Test and approve VoLTE service
  9. Distribute VoLTE service
Expected Results
  1. VoLTE service is created successfully
  2. VoLTE service is stored in catalog
  3. Service Creation event is sent via DMaaP
  4. Other modules (SO, VID, Usecase UI, CLAMP, VID, etc) receives the event
  5. VoLTE service is retrieved from SDC catalog by other modules
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00012: Closed Loop Configuration

Test Case IdV00012
Test Case NameClosed loop configuration
DescriptionThis test uses CLAMP to configure closed loop for VoLTE
ReleaseAmsterdam
Preconditions
  1. DCAE template has been imported (R1 SDC doesn't support DCAE template design)
  2. Holmes blueprint has been imported
  3. Holmes correlation rules have been defined
Testing Steps
  1. In CLAMP, choose which VNF and event to monitor
  2. Bring up CLAMP configuration policy GUI and copy Holmes correlation rules in it
  3. Bring up CLAMP provisional policy GUI and define reboot provisional policy
  4. Save the configuration
Expected Results
  1. Closed loop template and blueprint for Holmes are distributed to DCAE
  2. Configuration policy has been distributed to DCAE
  3. Provisional policy has been distributed to Policy engine
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00013: VoLTE Service Instantiation

Test Case IdV00013
Test Case NameVoLTE Service Instantiation
DescriptionThis test covers the whole VoLTE service instantiation process
ReleaseAmsterdam
Preconditions
  1. VoLTE service has been created, V00011 has passed
  2. Closed loop has been configured, V00012 has passed
  3. PEs have been configured and integrated with corresponding SDN WAN controller
  4. DC GWs have been configured and integrated with corresponding SDN local controller
Testing Steps
  1. ONAP user uses Usecase UI GUI to start VoLTE service instantiation
  2. 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
  3. 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
  4. 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
  1. vEPC service is instantiated successfully, including all vEPC VNFs and VLs
  2. vIMS service is instantiated successfully, including all vIMS VNFs and VLs
  3. WAN service is instantiated successfully, including underlay and overlay networks
  4. Holmes analytics container is brought up correctly by DCAE
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00014: VoLTE Auto-healing

Test Case IdV00014
Test Case NameVoLTE Auto-healing
DescriptionThis test covers the closed loop with alarm correlation and auto-healing
ReleaseAmsterdam
Preconditions
  1. VoLTE service has been instantiated
  2. VoLTE closed loop has been configured and started
  3. SPGW VNF supports event generation
  4. VNF guest OS supports event generation
  5. MultiVIM supports event collection from guest OS and event forwarding
Testing Steps
  1. Use Robot test script to shutdown standby MPU VM inside SPGW VNF
Expected Results
  1. EMS collects standby MPU offline event from SPGW VNF and sends the event to VFC
  2. 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
  3. Holmes receives MPU offline events
  4. Holmes receives MPU guest OS heartbeat missing events
  5. Holmes does correlation of the two types of events and generate one signature event and sends it to Policy
  6. Policy triggers provisional policy and reboot action is sent to VFC
  7. VFC uses VNFM driver to reboot standby MPU VM
  8. Standby MPU is reboot
  9. Clear event is sent from SPGW VNF about standby MPU back online
  10. Heartbeat from standby MPU VM is received by MultiVIM and clear event is sent by MultiVIM about heartbeat recovery
  11. Holmes does the event correlation and sends Clear signature event to Policy
  12. Policy stops the reboot action
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


V00015: VoLTE Service Termination

Test Case IdV00015
Test Case NameVoLTE Service Termination
DescriptionThis test covers VoLTE service termination process
ReleaseAmsterdam
Preconditions
  1. VoLTE service has been created
  2. Closed loop has been configured and started
  3. PEs have been configured and integrated with corresponding SDN WAN controller
  4. DC GWs have been configured and integrated with corresponding SDN local controller
Testing Steps
  1. ONAP user uses Usecase UI GUI to remove VoLTE service
Expected Results
  1. vEPC service is removed successfully, including all vEPC VNFs and VLs
  2. vIMS service is removed successfully, including all vIMS VNFs and VLs
  3. WAN service is removed successfully, including underlay and overlay networks
  4. Closed loop is stopped
  5. Holmes analytics container is removed by DCAE
  6. Closed loop related artifacts (including DCAE template, configurational policy and provisional policy, DG, workflows) are removed from ONAP
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name




  • No labels