summaryrefslogtreecommitdiffstats
path: root/docs/userguide/opnfv_yardstick_tc008.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/userguide/opnfv_yardstick_tc008.rst')
-rw-r--r--docs/userguide/opnfv_yardstick_tc008.rst90
1 files changed, 0 insertions, 90 deletions
diff --git a/docs/userguide/opnfv_yardstick_tc008.rst b/docs/userguide/opnfv_yardstick_tc008.rst
deleted file mode 100644
index a4ecaf6ae..000000000
--- a/docs/userguide/opnfv_yardstick_tc008.rst
+++ /dev/null
@@ -1,90 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International
-.. License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) OPNFV, Ericsson AB and others.
-
-*************************************
-Yardstick Test Case Description TC008
-*************************************
-
-.. _pktgen: https://www.kernel.org/doc/Documentation/networking/pktgen.txt
-
-+-----------------------------------------------------------------------------+
-|Packet Loss Extended Test |
-| |
-+--------------+--------------------------------------------------------------+
-|test case id | OPNFV_YARDSTICK_TC008_NW PERF, Packet loss Extended Test |
-| | |
-+--------------+--------------------------------------------------------------+
-|metric | Number of flows, packet size and throughput |
-| | |
-+--------------+--------------------------------------------------------------+
-|test purpose | To evaluate the IaaS network performance with regards to |
-| | flows and throughput, such as if and how different amounts |
-| | of packet sizes and flows matter for the throughput between |
-| | VMs on different compute blades. Typically e.g. the |
-| | performance of a vSwitch |
-| | depends on the number of flows running through it. Also |
-| | performance of other equipment or entities can depend |
-| | on the number of flows or the packet sizes used. |
-| | The purpose is also to be able to spot trends. Test results, |
-| | graphs ans similar shall be stored for comparison reasons and|
-| | product evolution understanding between different OPNFV |
-| | versions and/or configurations. |
-| | |
-+--------------+--------------------------------------------------------------+
-|configuration | file: opnfv_yardstick_tc008.yaml |
-| | |
-| | Packet size: 64, 128, 256, 512, 1024, 1280 and 1518 bytes. |
-| | |
-| | Number of ports: 1, 10, 50, 100, 500 and 1000. The amount of |
-| | configured ports map from 2 up to 1001000 flows, |
-| | respectively. Each packet_size/port_amount combination is run|
-| | ten times, for 20 seconds each. Then the next |
-| | packet_size/port_amount combination is run, and so on. |
-| | |
-| | The client and server are distributed on different HW. |
-| | |
-| | For SLA max_ppm is set to 1000. |
-| | |
-+--------------+--------------------------------------------------------------+
-|test tool | pktgen |
-| | |
-| | (Pktgen is not always part of a Linux distribution, hence it |
-| | needs to be installed. It is part of the Yardstick Docker |
-| | image. |
-| | As an example see the /yardstick/tools/ directory for how |
-| | to generate a Linux image with pktgen included.) |
-| | |
-+--------------+--------------------------------------------------------------+
-|references | pktgen_ |
-| | |
-| | ETSI-NFV-TST001 |
-| | |
-+--------------+--------------------------------------------------------------+
-|applicability | Test can be configured with different packet sizes, amount |
-| | of flows and test duration. Default values exist. |
-| | |
-| | SLA (optional): max_ppm: The number of packets per million |
-| | packets sent that are acceptable to loose, not received. |
-| | |
-+--------------+--------------------------------------------------------------+
-|pre-test | The test case image needs to be installed into Glance |
-|conditions | with pktgen 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. pktgen 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. |
-| | |
-+--------------+--------------------------------------------------------------+