Page tree
Skip to end of metadata
Go to start of metadata

The HA team is cooperating with the Yardstick team on developing multiple HA test cases. These test cases are continious enriched and developed. Below are detaied info about the test cases.

Detailed Test Cases Discription

 

Yardstick Test Case Description TC019?Control Node Openstack Service High Availability

 http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc019.html

Yardstick Test Case Description TC025?OpenStack Controller Node abnormally shutdown High Availability

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc025.html

Yardstick Test Case Description TC045?Control Node Openstack Service High Availability - Neutron Server

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc045.html

Yardstick Test Case Description TC046?Control Node Openstack Service High Availability - Keystone

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc046.html

Yardstick Test Case Description TC047?Control Node Openstack Service High Availability - Glance Api

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc047.html

Yardstick Test Case Description TC048?Control Node Openstack Service High Availability - Cinder Api

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc048.html

Yardstick Test Case Description TC049?Control Node Openstack Service High Availability - Swift Proxy

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc049.html

Yardstick Test Case Description TC050?OpenStack Controller Node Network High Availability

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc050.html

Yardstick Test Case Description TC051?OpenStack Controller Node CPU Overload High Availability

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc051.html

Yardstick Test Case Description TC052?OpenStack Controller Node Disk I/O Block High Availability

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc052.html

Yardstick Test Case Description TC053?OpenStack Controller Load Balance Service High Availability

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc053.html

Yardstick Test Case Description TC054?OpenStack Virtual IP High Availability

http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/opnfv_yardstick_tc054.html

 

General test case information for Dovetail

  1. Provide a high level description of the test area, main features being tested, and answer why it is in scope for Dovetail Danube. If there is a subset that is in scope, describe the subset.
    The High availability test cases focus on the availability testing for OPNFV platform. Currently most of test cases are focusing on Openstack HA, including multiple services in OpenStack, such as nova, neutron and etc.. There are also test cases on I/O, and CPU. These testcases are released mostly in Colorado. And the HA testing framework is reshaped in Danube. We see these test cases as basic HA testing for OPNFV, making sure the platform meet the Carrier-Grade availability requirement. The test cases will extend in future releases and more HA aspects will be taken into consideration.
  2. Describe how the features are tested, and justify why it is appropriate methodology for compliance testing. If modification or enhancement are needed, please describe the work needed in Dovetail.
    The test cases mainly include an attacker and a monitor. The attacker is responsible for creating the failure. Monitor is responsible for monitoring the certain service under test and see if it could recover within SLA. After testing, there is a certain recovery process that help the whole system recover to the  initial state.
  3. Describe how the automated test cases are implemented, and why it is appropriate for compliance testing. If modification or enhancement are needed, please describe the work needed in Dovetail
     Currently the HA testcases are included in Yardstick.
  4. Describe test results, pass/fail criteria
    The test result is pass if the monitor finds out the service under testing recovers within SLA.
  5. Describe the conditions that the SUT must be in for the test cases to run. Are the test cases executable in a limited subset of OPNFV Scenarios only? If so, which subset have the pre-conditions met to pass?
    The SUT should follow the HA scenarios in the OPNFV releases.
  6. Provide a link of pass test run results /  examples, if any.
  7. Any other important information or comments
  • No labels