aboutsummaryrefslogtreecommitdiffstats
path: root/tests/opnfv/test_suites/opnfv_os-odl_l2-bgpvpn-noha_daily.yaml
blob: 372012928028cfb8a3dcbef6cb4e8b80015c060b (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

##############################################################################
# Copyright (c) 2017 mskalski@mirantis.com and others.
#
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Apache License, Version 2.0
# which accompanies this distribution, and is available at
# http://www.apache.org/licenses/LICENSE-2.0
##############################################################################
---
# os-odl_l2-bgpvpn-noha daily task suite

schema: "yardstick:suite:0.1"

name: "os-odl_l2-bgpvpn-noha"
test_cases_dir: "tests/opnfv/test_cases/"
test_cases:
-
  file_name: opnfv_yardstick_tc043.yaml
  constraint:
      installer: fuel
      pod: ericsson-pod2
  task_args:
      ericsson-pod2: '{"file": "etc/yardstick/nodes/fuel_baremetal/pod.yaml",
      "host": "node1.LF","target": "node2.LF"}'
-
  file_name: opnfv_yardstick_tc002.yaml
-
  file_name: opnfv_yardstick_tc005.yaml
ss="cp">.. (c) OPNFV, Yin Kanglin and others. .. 14_ykl@tongji.edu.cn ************************************* Yardstick Test Case Description TC049 ************************************* +-----------------------------------------------------------------------------+ |Control Node Openstack Service High Availability - Swift Proxy | | | +--------------+--------------------------------------------------------------+ |test case id | OPNFV_YARDSTICK_TC049: Control node Openstack service down - | | | swift proxy | +--------------+--------------------------------------------------------------+ |test purpose | This test case will verify the high availability of the | | | storage service provided by OpenStack (swift-proxy) on | | | control node. | | | | +--------------+--------------------------------------------------------------+ |test method | This test case kills the processes of swift-proxy service on | | | a selected control node, then checks whether the request of | | | the related Openstack command is OK and the killed processes | | | are recovered. | | | | +--------------+--------------------------------------------------------------+ |attackers | In this test case, an attacker called "kill-process" is | | | needed. This attacker includes three parameters: | | | 1) fault_type: which is used for finding the attacker's | | | scripts. It should be always set to "kill-process" in this | | | test case. | | | 2) process_name: which is the process name of the specified | | | OpenStack service. If there are multiple processes use the | | | same name on the host, all of them are killed by this | | | attacker. | | | In this case. This parameter should always set to "swift- | | | proxy". | | | 3) host: which is the name of a control node being attacked. | | | | | | e.g. | | | -fault_type: "kill-process" | | | -process_name: "swift-proxy" | | | -host: node1 | | | | +--------------+--------------------------------------------------------------+ |monitors | In this test case, two kinds of monitor are needed: | | | 1. the "openstack-cmd" monitor constantly request a specific | | | Openstack command, which needs two parameters: | | | 1) monitor_type: which is used for finding the monitor class | | | and related scritps. It should be always set to | | | "openstack-cmd" for this monitor. | | | 2) command_name: which is the command name used for request. | | | In this case, the command name should be swift related | | | commands. | | | | | | 2. the "process" monitor check whether a process is running | | | on a specific node, which needs three parameters: | | | 1) monitor_type: which used for finding the monitor class and| | | related scritps. It should be always set to "process" | | | for this monitor. | | | 2) process_name: which is the process name for monitor | | | 3) host: which is the name of the node runing the process | | | | | | e.g. | | | monitor1: | | | -monitor_type: "openstack-cmd" | | | -command_name: "swift stat" | | | monitor2: | | | -monitor_type: "process" | | | -process_name: "swift-proxy" | | | -host: node1 | | | | +--------------+--------------------------------------------------------------+ |metrics | In this test case, there are two metrics: | | | 1)service_outage_time: which indicates the maximum outage | | | time (seconds) of the specified Openstack command request. | | | 2)process_recover_time: which indicates the maximun time | | | (seconds) from the process being killed to recovered | | | | +--------------+--------------------------------------------------------------+ |test tool | Developed by the project. Please see folder: | | | "yardstick/benchmark/scenarios/availability/ha_tools" | | | | +--------------+--------------------------------------------------------------+ |references | ETSI NFV REL001 | | | | +--------------+--------------------------------------------------------------+ |configuration | This test case needs two configuration files: | | | 1) test case file: opnfv_yardstick_tc049.yaml | | | -Attackers: see above "attackers" discription | | | -waiting_time: which is the time (seconds) from the process | | | being killed to stoping monitors the monitors | | | -Monitors: see above "monitors" discription | | | -SLA: see above "metrics" discription | | | | | | 2)POD file: pod.yaml | | | The POD configuration should record on pod.yaml first. | | | the "host" item in this test case will use the node name in | | | the pod.yaml. | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | start monitors: | | | each monitor will run with independently process | | | | | | Result: The monitor info will be collected. | | | | +--------------+--------------------------------------------------------------+ |step 2 | do attacker: connect the host through SSH, and then execute | | | the kill process script with param value specified by | | | "process_name" | | | | | | Result: Process will be killed. | | | | +--------------+--------------------------------------------------------------+ |step 3 | stop monitors after a period of time specified by | | | "waiting_time" | | | | | | Result: The monitor info will be aggregated. | | | | +--------------+--------------------------------------------------------------+ |step 4 | verify the SLA | | | | | | Result: The test case is passed or not. | | | | +--------------+--------------------------------------------------------------+ |post-action | It is the action when the test cases exist. It will check the| | | status of the specified process on the host, and restart the | | | process if it is not running for next test cases | | | | +--------------+--------------------------------------------------------------+ |test verdict | Fails only if SLA is not passed, or if there is a test case | | | execution problem. | | | | +--------------+--------------------------------------------------------------+