summaryrefslogtreecommitdiffstats
path: root/upstream
diff options
context:
space:
mode:
authorJonas Bjurel <jonas.bjurel@ericsson.com>2016-09-26 16:50:00 +0000
committerGerrit Code Review <gerrit@172.30.200.206>2016-09-26 16:50:00 +0000
commitf91768399ba14f99912e4e318aa685496c531c32 (patch)
tree2a18fc11f956d39ed006b26d12942e801f804cab /upstream
parent705616e9a66f54a8963d8e8c5e9fc1dd99aa2f05 (diff)
Updated armband
Project: fuel d53f15a6dacb5e3d3fd58002692f9c08256ff1e9 Enable ci off-line deployment Updated dea_base to use locak repo mirrors for off-line deployment NOT TO BE PART OF COLORADO.1 Change-Id: Ia8e2d716570267ed9a9e06e253b6a7b258ee26eb Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com> (cherry picked from commit caee61817eb7f4235ca33a9da12f14a285f9e012)
Diffstat (limited to 'upstream')
m---------upstream/fuel0
1 files changed, 0 insertions, 0 deletions
diff --git a/upstream/fuel b/upstream/fuel
-Subproject 0a76d88bcd02fcfe4678310e7d8a6ffdbabfd48
+Subproject d53f15a6dacb5e3d3fd58002692f9c08256ff1e
f='#n141'>141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, Huawei Technologies Co.,Ltd and others.

*************************************
Yardstick Test Case Description TC074
*************************************

.. _Storperf: https://wiki.opnfv.org/display/storperf/Storperf

+-----------------------------------------------------------------------------+
|Storperf                                                                     |
|                                                                             |
+--------------+--------------------------------------------------------------+
|test case id  | OPNFV_YARDSTICK_TC074_Storperf                               |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|metric        | Storage performance                                          |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test purpose  | To evaluate and report on the Cinder volume performance.     |
|              |                                                              |
|              | This testcase integrates with OPNFV StorPerf to measure      |
|              | block performance of the underlying Cinder drivers.  Many    |
|              | options are supported, and even the root disk (Glance        |
|              | ephemeral storage can be profiled.                           |
|              |                                                              |
|              | The fundamental concept of the test case is to first fill    |
|              | the volumes with random data to ensure reported metrics      |
|              | are indicative of continued usage and not skewed by          |
|              | transitional performance while the underlying storage        |
|              | driver allocates blocks.                                     |
|              | The metrics for filling the volumes with random data         |
|              | are not reported in the final results.  The test also        |
|              | ensures the volumes are performing at a consistent level     |
|              | of performance by measuring metrics every minute, and        |
|              | comparing the trend of the metrics over the run.  By         |
|              | evaluating the min and max values, as well as the slope of   |
|              | the trend, it can make the determination that the metrics    |
|              | are stable, and not fluctuating beyond industry standard     |
|              | norms.                                                       |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|configuration | file: opnfv_yardstick_tc074.yaml                             |
|              |                                                              |
|              | * agent_count: 1 - the number of VMs to be created           |
|              | * agent_image: "Ubuntu-14.04" - image used for creating VMs  |
|              | * public_network: "ext-net" - name of public network         |
|              | * volume_size: 2 - cinder volume size                        |
|              | * block_sizes: "4096" - data block size                      |
|              | * queue_depths: "4" - the number of simultaneous I/Os        |
|              |   to perform at all times                                    |
|              | * StorPerf_ip: "192.168.200.2"                               |
|              | * query_interval: 10 - state query interval                  |
|              | * timeout: 600 - maximum allowed job time                    |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test tool     | Storperf_                                                    |
|              |                                                              |
|              | StorPerf is a tool to measure block and object storage       |
|              | performance in an NFVI.                                      |
|              |                                                              |
|              | StorPerf is delivered as a Docker container from             |
|              | https://hub.docker.com/r/opnfv/storperf-master/tags/.        |
|              |                                                              |
|              | The underlying tool used is FIO, and StorPerf supports       |
|              | any FIO option in order to tailor the test to the exact      |
|              | workload needed.                                             |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|references    | Storperf_                                                    |
|              |                                                              |
|              | ETSI-NFV-TST001                                              |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|applicability | Test can be configured with different:                       |
|              |                                                              |
|              | * agent_count                                                |
|              | * volume_size                                                |
|              | * block_sizes                                                |
|              | * queue_depths                                               |
|              | * query_interval                                             |
|              | * timeout                                                    |
|              | * target=[device or path]                                    |
|              |   The path to either an attached storage device              |
|              |   (/dev/vdb, etc) or a directory path  (/opt/storperf) that  |
|              |   will be used to execute the performance test. In the case  |
|              |   of a device, the entire device will be used. If not        |
|              |   specified, the current directory will be used.             |
|              | * workload=[workload module]                                 |
|              |   If not specified, the default is to run all workloads. The |
|              |   workload types are:                                        |
|              |      - rs: 100% Read, sequential data                        |
|              |      - ws: 100% Write, sequential data                       |
|              |      - rr: 100% Read, random access                          |
|              |      - wr: 100% Write, random access                         |
|              |      - rw: 70% Read / 30% write, random access               |
|              |   measurements.                                              |
|              | * workloads={json maps}                                      |
|              |   This parameter supercedes the workload and calls the V2.0  |
|              |   API in StorPerf. It allows for greater control of the      |
|              |   parameters to be passed to FIO.  For example, running a    |
|              |   random read/write with a mix of 90% read and 10% write     |
|              |   would be expressed as follows:                             |
|              |   {"9010randrw": {"rw":"randrw","rwmixread": "90"}}          |
|              |   Note: This must be passed in as a string, so don't forget  |
|              |   to escape or otherwise properly deal with the quotes.      |
|              |                                                              |
|              | * report= [job_id]                                           |
|              |   Query the status of the supplied job_id and report on      |
|              |   metrics. If a workload is supplied, will report on only    |
|              |   that subset.                                               |
|              | * availability_zone: Specify the availability zone which     |
|              |   the stack will use to create instances.                    |
|              | * volume_type:                                               |
|              |   Cinder volumes can have different types, for example       |
|              |   encrypted vs. not encrypted.                               |
|              |   To be able to profile the difference between the two.      |
|              | * subnet_CIDR: Specify subnet CIDR of private network        |
|              | * stack_name: Specify the name of the stack that will be     |
|              |   created, the default: "StorperfAgentGroup"                 |
|              | * volume_count: Specify the number of volumes per            |
|              |   virtual machines                                           |
|              |                                                              |
|              |   There are default values for each above-mentioned option.  |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|pre-test      | If you do not have an Ubuntu 14.04 image in Glance, you will |
|conditions    | need to add one.                                             |
|              |                                                              |
|              | Storperf is required to be installed in the environment.     |
|              | There are two possible methods for Storperf installation:    |
|              |     Run container on Jump Host                               |
|              |     Run container in a VM                                    |
|              |                                                              |
|              | Running StorPerf on Jump Host                                |
|              | Requirements:                                                |
|              |     - Docker must be installed                               |
|              |     - Jump Host must have access to the OpenStack Controller |
|              |       API                                                    |
|              |     - Jump Host must have internet connectivity for          |
|              |       downloading docker image                               |
|              |     - Enough floating IPs must be available to match your    |
|              |       agent count                                            |
|              |                                                              |
|              | Running StorPerf in a VM                                     |
|              | Requirements:                                                |
|              |     - VM has docker installed                                |
|              |     - VM has OpenStack Controller credentials and can        |
|              |       communicate with the Controller API                    |
|              |     - VM has internet connectivity for downloading the       |
|              |       docker image                                           |
|              |     - Enough floating IPs must be available to match your    |
|              |       agent count                                            |
|              |                                                              |
|              | No POD specific requirements have been identified.           |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test sequence | description and expected result                              |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|step 1        | Yardstick calls StorPerf to create the heat stack with the   |
|              | number of VMs and size of Cinder volumes specified.  The     |
|              | VMs will be on their own private subnet, and take floating   |
|              | IP addresses from the specified public network.              |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|step 2        | Yardstick calls StorPerf to fill all the volumes with        |
|              | random data.                                                 |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|step 3        | Yardstick calls StorPerf to perform the series of tests      |
|              | specified by the workload, queue depths and block sizes.     |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|step 4        | Yardstick calls StorPerf to delete the stack it created.     |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test verdict  | None. Storage performance results are fetched and stored.    |
|              |                                                              |
+--------------+--------------------------------------------------------------+