docs/yardstick/opnfv_yardstick_tc008.rst

   1 *************************************
   2 Yardstick Test Case Description TC008
   3 *************************************
   4 +-----------------------------------------------------------------------------+
   5 |Network Performance                                                          |
   6 +==============+==============================================================+
   7 |test case id  | OPNFV_YARDSTICK_TC008_NW PERF, Packet loss Extended Test     |
   8 +--------------+--------------------------------------------------------------+
   9 |metric        | Number of flows, packet size and throughput                  |
  10 +--------------+--------------------------------------------------------------+
  11 |test purpose  | To evaluate the IaaS network performance with regards to     |
  12 |              | flows and throughput, such as if and how different amounts   |
  13 |              | of packet sizes and flows matter for the throughput between  |
  14 |              | VMs on different compute blades. Typically e.g. the          |
  15 |              | performance of a vSwitch                                     |
  16 |              | depends on the number of flows running through it. Also      |
  17 |              | performance of other equipment or entities can depend        |
  18 |              | on the number of flows or the packet sizes used.             |
  19 |              | The purpose is also to be able to spot trends. Test results, |
  20 |              | graphs ans similar shall be stored for comparison reasons and|
  21 |              | product evolution understanding between different OPNFV      |
  22 |              | versions and/or configurations.                              |
  23 +--------------+--------------------------------------------------------------+
  24 |configuration | file: opnfv_yardstick_tc008.yaml                             |
  25 |              |                                                              |
  26 |              | Packet size: 64, 128, 256, 512, 1024, 1280 and 1518 bytes.   |
  27 |              |                                                              |
  28 |              | Number of ports: 1, 10, 50, 100, 500 and 1000. The amount of |
  29 |              | configured ports map from 2 up to 1001000 flows,             |
  30 |              | respectively. Each packet_size/port_amount combination is run|
  31 |              | ten times, for 20 seconds each. Then the next                |
  32 |              | packet_size/port_amount combination is run, and so on.       |
  33 |              |                                                              |
  34 |              | The client and server are distributed on different HW.       |
  35 |              |                                                              |
  36 |              | For SLA max_ppm is set to 1000.                              |
  37 +--------------+--------------------------------------------------------------+
  38 |test tool     | pktgen                                                       |
  39 |              |                                                              |
  40 |              | (Pktgen is not always part of a Linux distribution, hence it |
  41 |              | needs to be installed. It is part of the Yardstick Docker    |
  42 |              | image.                                                       |
  43 |              | As an example see the /yardstick/tools/ directory for how    |
  44 |              | to generate a Linux image with pktgen included.)             |
  45 +--------------+--------------------------------------------------------------+
  46 |references    |https://www.kernel.org/doc/Documentation/networking/pktgen.txt|
  47 |              |                                                              |
  48 |              |ETSI-NFV-TST001                                               |
  49 +--------------+--------------------------------------------------------------+
  50 |applicability | Test can be configured with different packet sizes, amount   |
  51 |              | of flows and test duration. Default values exist.            |
  52 |              |                                                              |
  53 |              |SLA (optional):                                               |
  54 |              |    max_ppm: The number of packets per million packets sent   |
  55 |              |             that are acceptable to lose, i.e. not received.  |
  56 +--------------+--------------------------------------------------------------+
  57 |pre-test      | The test case image needs to be installed into Glance        |
  58 |conditions    | with pktgen included in it.                                  |
  59 |              |                                                              |
  60 |              | No POD specific requirements have been identified.           |
  61 +--------------+------+----------------------------------+--------------------+
  62 |test sequence | step | description                      | result             |
  63 |              +------+----------------------------------+--------------------+
  64 |              |  1   | The hosts are installed, as      | Logs are stored    |
  65 |              |      | server and client. pktgen is     |                    |
  66 |              |      | invoked and logs are produced    |                    |
  67 |              |      | and stored.                      |                    |
  68 +--------------+------+----------------------------------+--------------------+
  69 |test verdict  | Fails only if SLA is not passed, or if there is a test case  |
  70 |              | execution problem.                                           |
  71 +--------------+--------------------------------------------------------------+