*************************************
Yardstick Test Case Description TC009
*************************************
+-----------------------------------------------------------------------------+
|Network Performance                                                          |
+==============+==============================================================+
|test case id  | OPNFV_YARDSTICK_TC009_NW PERF, Packet loss                   |
+--------------+--------------------------------------------------------------+
|metric        | Number of flows and throughput                               |
+--------------+--------------------------------------------------------------+
|test purpose  | To evaluate the IaaS network performance with regards to     |
|              | flows and throughput, such as if and how different amounts   |
|              | of 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_tc009.yaml                             |
|              |                                                              |
|              | Packet size: 64 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 port amount is run ten times, for 20      |
|              | seconds each. Then the next port_amount 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    |https://www.kernel.org/doc/Documentation/networking/pktgen.txt|
|              |                                                              |
|              |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 lose, i.e. 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 | step | description                      | result             |
|              +------+----------------------------------+--------------------+
|              |  1   | The hosts are installed, as      | Logs are stored    |
|              |      | server and client. pktgen is     |                    |
|              |      | invoked and logs are produced    |                    |
|              |      | and stored.                      |                    |
+--------------+------+----------------------------------+--------------------+
|test verdict  | Fails only if SLA is not passed, or if there is a test case  |
|              | execution problem.                                           |
+--------------+--------------------------------------------------------------+

.. only:: html

    Revision: 32b39d0f576dc5c71678fd0b6b8feab6f2173939

    Build date: |today|