Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Test Results @CMCC lab

Image Added

Category: External System Registration


V00001: WindRiver OpenStack VIM Registration

...

Test Case IdV00006
Test Case NameVendors' EMSs Registration
DescriptionRegister all VNF vendors' EMSs
ReleaseAmsterdam
Preconditions
  1. All VNF vendor's EMS have been installed and configured
Testing Steps
  1. Register all vendors' EMSs using ONAP ESR GUI with the needed information (IP, port, authentication information, etc)
Expected Results
  1. All EMSs are registered successfully with ONAP
  2. All EMSs information is stored correctly in ONAP
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Tester Name


Category: VNF Onboarding and Service Creation


V00007: VoLTE VNFs Onboarding

...

V00010: WAN Resource Onboarding (Need to finalize overlay and underlay are seperate VL resourcesUnderlay and Overlay templates are preloaded into SDC, this test case can be removed if not needed anymore)

Test Case IdV00010
Test Case NameWAN Resource Onboarding
DescriptionThis test onboards WAN resource using SDC
ReleaseAmsterdam
Preconditions
  1. WAN underlay network template (.yaml) has been defined and packaged in a CSAR file
  2. WAN overlay network template (.yaml) has been defined and packaged in a CSAR file
Testing Steps
  1. In SDC create a VL resource and upload WAN underlay network CSAR file. Make sure controllerInfo property is set to SDNC in the template
  2. In SDC create a VL resource and upload WAN overlay network CSAR file. Make sure controllerInfo property is set to SDNC
Expected Results
  1. WAN underlay network resource onboarded successfully and shown in catalog
  2. WAN overlay network resource onboarded successfully and shown in catalog
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name

...

Test Case IdV00012
Test Case NameClosed loop configuration
Description

This test uses CLAMP to configure closed loop for VoLTE. There are 4 configurations:

  1. Provisional rules for Policy
  2. Correlation rules for Holmes
  3. Holmes microservice Blueprint for DCAE
  4. VES configuration ?(in R1, there is no configuration needed)
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 VNF SPGW and events (VNF Fault and VM Fault) 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 healing 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


Category: Service Instantiation and Monitoring


V00013: VoLTE Service Instantiation

...

Test Case IdV00014
Test Case NameSystem Performance and Alarm Monitoring
DescriptionThis test uses Usecase UI GUI to monitor system performance and event
ReleaseAmsterdam
Preconditions
  1. VoLTE service has been instantiated
  2. Closed loop for VoLTE has been configured and started
Testing Steps
  1. ONAP user uses Usecase UI GUI to check system performance, such as CPU, memory and disk usage
  2. ONAP user views the VNF alarms collected by ONAP
Expected Results
  1. System performance (including system CPU, memory and disk usage) is shown on ONAP Usecase UI GUI
  2. VNF alarms, specified in CLAMP for the closed loop, are shown in Usecase UI GUI
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


Category: Closed Loop


V00015: VoLTE Auto-healing

Test Case IdV00015
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 Manually shutdown standby MPU VM inside SPGW VNF. This should trigger the VNF and VIM to generate alarms
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 healing action is sent to VFC
  7. VFC uses SVNFM driver to heal standby MPU VM
  8. Standby MPU is healed
  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 healing action
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name


Category: Service Termination


V00016: VoLTE Service Termination

...