aboutsummaryrefslogtreecommitdiffstats
path: root/vswitches/utils.py
blob: 7350de3166f832a8b479d454058691e91ccf1b4e (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
30
31
32
33
34
35
36
37
38
39
40
# Copyright 2015 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.

"""Utility functions for working with vSwitches and flows
"""

import copy

def add_ports_to_flow(flow, in_port, out_port):
    """Creates a new flow based on the given flow and adds in port and out port
    to it.

    The flow dictionary structure is described in IVswitch

    :param flow: Description of the flow as a dictionary
    :param in_port: OpenFlow number of the ingress port for the rule
    :param out_port: OpenFlow number of the eggress port for the rule

    :returns: A new dictionary describing a flow combining the parameters
    """
    new_flow = copy.deepcopy(flow)
    new_flow['in_port'] = in_port

    if 'actions' in new_flow:
        new_flow['actions'].append('output:' + str(out_port))
    else:
        new_flow['actions'] = ['output:' + str(out_port)]

    return new_flow
ecified control node, then checks whether all services | | | provided by the control node are OK with some monitor tools. | +--------------+--------------------------------------------------------------+ |attackers | In this test case, an attacker called "close-interface" 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 "close-interface" in | | | this test case. | | | 2) host: which is the name of a control node being attacked. | | | 3) interface: the network interface to be turned off. | | | | | | There are four instance of the "close-interface" monitor: | | | attacker1(for public netork): | | | -fault_type: "close-interface" | | | -host: node1 | | | -interface: "br-ex" | | | attacker2(for management netork): | | | -fault_type: "close-interface" | | | -host: node1 | | | -interface: "br-mgmt" | | | attacker3(for storage netork): | | | -fault_type: "close-interface" | | | -host: node1 | | | -interface: "br-storage" | | | attacker4(for private netork): | | | -fault_type: "close-interface" | | | -host: node1 | | | -interface: "br-mesh" | +--------------+--------------------------------------------------------------+ |monitors | In this test case, the monitor named "openstack-cmd" is | | | needed. The monitor needs 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" | | | -command_name: "nova image-list" | | | monitor2: | | | -monitor_type: "openstack-cmd" | | | -command_name: "neutron router-list" | | | monitor3: | | | -monitor_type: "openstack-cmd" | | | -command_name: "heat stack-list" | | | monitor4: | | | -monitor_type: "openstack-cmd" | | | -command_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_tc050.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 turnoff network interface script with param value | | | specified by "interface". | | | | | | Result: Network interfaces will be turned down. | | | | +--------------+--------------------------------------------------------------+ |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 turns up the | | | network interface of the control node if it is not turned | | | up. | +--------------+--------------------------------------------------------------+ |test verdict | Fails only if SLA is not passed, or if there is a test case | | | execution problem. | | | | +--------------+--------------------------------------------------------------+