2.16.2.27. Yardstick Test Case Description TC074¶
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
|
test tool |
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 |
ETSI-NFV-TST001 |
applicability |
Test can be configured with different:
|
pre-test conditions |
If you do not have an Ubuntu 14.04 image in Glance, you will need to add one. Storperf is required to be installed in the environment. There are two possible methods for Storperf installation:
Running StorPerf on Jump Host Requirements:
Running StorPerf in a VM Requirements:
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. |