diff options
| author |   QiLiang <liangqi1@huawei.com> | 2016-01-11 06:24:12 +0000 |
|---|---|---|
| committer | QiLiang <liangqi1@huawei.com> | 2016-01-11 07:58:21 +0000 |
| commit | 738fb0942c39e5f1ecad87ae9dd776f1019d2491 (patch) | |
| tree | 3dca615bf6d2ae7928078f66d778b9b3db3fa5d8 /docs/configguide/yardstick_testcases/opnfv_yardstick_tc005.rst | |
| parent | a33f57371c740e0ab749bfffa4d31c08ef5c5b74 (diff) | |
Add test case description and task file for TC005
JIRA: YARDSTICK-93
Change-Id: I74adef0e6bae52a7080479d7054a92342f7324a7
Signed-off-by: QiLiang <liangqi1@huawei.com>
Diffstat (limited to 'docs/configguide/yardstick_testcases/opnfv_yardstick_tc005.rst')
| -rw-r--r-- | docs/configguide/yardstick_testcases/opnfv_yardstick_tc005.rst | 72 |
1 files changed, 72 insertions, 0 deletions
diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc005.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc005.rst new file mode 100644 index 000000000..8b7474696 --- /dev/null +++ b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc005.rst @@ -0,0 +1,72 @@ +************************************* +Yardstick Test Case Description TC005 +************************************* + +.. _fio: http://www.bluestop.org/fio/HOWTO.txt + ++-----------------------------------------------------------------------------+ +|Storage Performance | +| | ++--------------+--------------------------------------------------------------+ +|test case id | OPNFV_YARDSTICK_TC005_Storage Performance | +| | | ++--------------+--------------------------------------------------------------+ +|metric | IOPS, throughput and latency | +| | | ++--------------+--------------------------------------------------------------+ +|test purpose | To evaluate the IaaS storage performance with regards to | +| | IOPS, throughput and latency. | +| | The purpose is also to be able to spot trends. Test results, | +| | graphs and similar shall be stored for comparison reasons | +| | and product evolution understanding between different OPNFV | +| | versions and/or configurations. | +| | | ++--------------+--------------------------------------------------------------+ +|configuration | file: opnfv_yardstick_tc005.yaml | +| | | +| | IO types: read, write, randwrite, randread, rw | +| | IO block size: 4KB, 64KB, 1024KB, where each | +| | runs for 30 seconds(10 for ramp time, 20 for runtime). | +| | | +| | For SLA minimum read/write iops is set to 100, minimum | +| | read/write throughput is set to 400 KB/s, and maximum | +| | read/write latency is set to 20000 usec. | +| | | ++--------------+--------------------------------------------------------------+ +|test tool | fio | +| | | +| | (fio is not always part of a Linux distribution, hence it | +| | needs to be installed. As an example see the | +| | /yardstick/tools/ directory for how to generate a Linux | +| | image with fio included.) | +| | | ++--------------+--------------------------------------------------------------+ +|references | fio_ | +| | | +| | ETSI-NFV-TST001 | +| | | ++--------------+--------------------------------------------------------------+ +|applicability | Test can be configured with different read/write types, IO | +| | block size, IO depth, ramp time (runtime required for stable | +| | results) and test duration. Default values exist. | +| | | ++--------------+--------------------------------------------------------------+ +|pre-test | The test case image needs to be installed into Glance | +|conditions | with fio included in it. | +| | | +| | No POD specific requirements have been identified. | +| | | ++--------------+--------------------------------------------------------------+ +|test sequence | description and expected result | +| | | ++--------------+--------------------------------------------------------------+ +|step 1 | The hosts are installed, as server and client. fio is | +| | invoked and logs are produced and stored. | +| | | +| | Result: Logs are stored. | +| | | ++--------------+--------------------------------------------------------------+ +|test verdict | Fails only if SLA is not passed, or if there is a test case | +| | execution problem. | +| | | ++--------------+--------------------------------------------------------------+ |