diff options
| author |   Per Holmgren <per.q.holmgren@ericsson.com> | 2015-12-11 13:12:04 +0100 |
|---|---|---|
| committer |   Jörgen Karlsson <jorgen.w.karlsson@ericsson.com> | 2015-12-18 12:14:12 +0000 |
| commit | d70a4891900e5cf5017a718f4e9c8e3d9ea4fcb5 (patch) | |
| tree | df0c3cb434187b93de8e98529c29adc75cb0948f /docs | |
| parent | 0c98e8f83d3548f4f2dc91cfc6e743833fb635c9 (diff) | |
Adds Yardstick test case TC008, Network Performance Extended Tests
New test case using pktgen tool. Based on TC001, but with additional
packet sizes and more repetitions of each test combination,
respectively. Test case takes approx.3 hours to complete.
Change-Id: Iba2de5efa33d6e2c960772fa5345595f6d7ab4e6
JIRA: YARDSTICK-80
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/yardstick/opnfv_yardstick_tc008.rst | 71 |
1 files changed, 71 insertions, 0 deletions
diff --git a/docs/yardstick/opnfv_yardstick_tc008.rst b/docs/yardstick/opnfv_yardstick_tc008.rst new file mode 100644 index 000000000..f4971fbad --- /dev/null +++ b/docs/yardstick/opnfv_yardstick_tc008.rst @@ -0,0 +1,71 @@ +************************************* +Yardstick Test Case Description TC008 +************************************* ++-----------------------------------------------------------------------------+ +|Network Performance | ++==============+==============================================================+ +|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 |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. | ++--------------+--------------------------------------------------------------+ |