aboutsummaryrefslogtreecommitdiffstats
path: root/ansible/roles/download_samplevnfs/tasks/main.yml
blob: e9d4142c9a4d2f24c250f975a27c432d0033d252 (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
29
# Copyright (c) 2017 Intel Corporation.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
---
#- debug:
#    var: samplevnf_version
#    verbosity: 2

- name: fetch samplevnf
  git:
    repo: "{{ samplevnf_url }}"
    dest: "{{ samplevnf_dest }}"
    version: "{{ samplevnf_version }}"
    accept_hostkey: yes
    recursive: no
    force: yes

- set_fact:
    samplevnf_path: "{{ samplevnf_dest }}"
| +--------------+--------------------------------------------------------------+ |test method | This test case shutdowns a specified controller node with | | | some fault injection tools, then checks whether all services | | | provided by the controller node are OK with some monitor | | | tools. | | | | +--------------+--------------------------------------------------------------+ |attackers | In this test case, an attacker called "host-shutdown" is | | | needed. This attacker includes two parameters: | | | 1) fault_type: which is used for finding the attacker's | | | scripts. It should be always set to "host-shutdown" in | | | this test case. | | | 2) host: the name of a controller node being attacked. | | | | | | e.g. | | | -fault_type: "host-shutdown" | | | -host: node1 | | | | +--------------+--------------------------------------------------------------+ |monitors | In this test case, one kind 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 | | | | | | There are four instance of the "openstack-cmd" monitor: | | | monitor1: | | | -monitor_type: "openstack-cmd" | | | -api_name: "nova image-list" | | | monitor2: | | | -monitor_type: "openstack-cmd" | | | -api_name: "neutron router-list" | | | monitor3: | | | -monitor_type: "openstack-cmd" | | | -api_name: "heat stack-list" | | | monitor4: | | | -monitor_type: "openstack-cmd" | | | -api_name: "cinder list" | | | | +--------------+--------------------------------------------------------------+ |metrics | In this test case, there is one metric: | | | 1)service_outage_time: which indicates the maximum outage | | | time (seconds) of the specified Openstack command request. | | | | +--------------+--------------------------------------------------------------+ |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_tc019.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 | | | shutdown script on the host | | | | | | Result: The host will be shutdown. | | | | +--------------+--------------------------------------------------------------+ |step 3 | stop monitors after a period of time specified by | | | "waiting_time" | | | | | | Result: All monitor result 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 restarts the | | | specified controller node if it is not restarted. | | | | +--------------+--------------------------------------------------------------+ |test verdict | Fails only if SLA is not passed, or if there is a test case | | | execution problem. | | | | +--------------+--------------------------------------------------------------+