diff options
Diffstat (limited to 'docs/userguide/testusage.rst')
| -rw-r--r-- | docs/userguide/testusage.rst | 98 |
1 files changed, 60 insertions, 38 deletions
diff --git a/docs/userguide/testusage.rst b/docs/userguide/testusage.rst index 721fd635..c6037aaf 100644 --- a/docs/userguide/testusage.rst +++ b/docs/userguide/testusage.rst @@ -21,23 +21,19 @@ support in VSPERF includes: - Moongen software traffic generator. Requires a separate machine running moongen to execute packet generation. -If you want to use another traffic generator, please select the Dummy generator -option as shown in `Traffic generator instructions -<http://artifacts.opnfv.org/vswitchperf/docs/configguide/trafficgen.html>`__ +If you want to use another traffic generator, please select the :ref:`trafficgen-dummy` +generator. VSPERF Installation ^^^^^^^^^^^^^^^^^^^ To see the supported Operating Systems, vSwitches and system requirements, -please follow the `installation instructions -<http://artifacts.opnfv.org/vswitchperf/docs/configguide/installation.html>`__ to -install. +please follow the `installation instructions <vsperf-installation>`. Traffic Generator Setup ^^^^^^^^^^^^^^^^^^^^^^^ -Follow the `Traffic generator instructions -<http://artifacts.opnfv.org/vswitchperf/docs/configguide/trafficgen.html>`__ to +Follow the `Traffic generator instructions <trafficgen-installation>` to install and configure a suitable traffic generator. Cloning and building src dependencies @@ -86,8 +82,8 @@ contents. Any configuration item mentioned in any .conf file in the custom configuration value. Further details about configuration files evaluation and special behaviour -of options with ``GUEST_`` prefix could be found at `design document -<http://artifacts.opnfv.org/vswitchperf/docs/design/vswitchperf_design.html#configuration>`__. +of options with ``GUEST_`` prefix could be found at :ref:`design document +<design-configuration>`. Using a custom settings file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -111,8 +107,10 @@ described like so (1 = max priority): 4. Configuration file(s) Further details about configuration files evaluation and special behaviour -of options with ``GUEST_`` prefix could be found at `design document -<http://artifacts.opnfv.org/vswitchperf/docs/design/vswitchperf_design.html#configuration>`__. +of options with ``GUEST_`` prefix could be found at :ref:`design document +<design-configuration>`. + +.. _overriding-parameters-documentation: Overriding values defined in configuration files ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -163,27 +161,14 @@ section of test case definition. It is also forbidden to redefine a value of vloop_vnf ^^^^^^^^^ -vsperf uses a VM image called vloop_vnf for looping traffic in the deployment +VSPERF uses a VM image called vloop_vnf for looping traffic in the deployment scenarios involving VMs. The image can be downloaded from `<http://artifacts.opnfv.org/>`__. -.. code-block:: console - - $ wget http://artifacts.opnfv.org/vswitchperf/vloop-vnf-ubuntu-14.04_20151216.qcow2 - -Newer vloop_vnf images are available. Please reference the -installation instructions for information on these images -`installation instructions -<http://artifacts.opnfv.org/vswitchperf/docs/configguide/installation.html>`__ - - -vloop_vnf forwards traffic through a VM using one of: +Please see the installation instructions for information on :ref:`vloop-vnf` +images. -* DPDK testpmd -* Linux Bridge -* l2fwd kernel Module. - -Alternatively you can use your own QEMU image. +.. _l2fwd-module: l2fwd Kernel Module ^^^^^^^^^^^^^^^^^^^ @@ -350,6 +335,43 @@ To run tests using Vanilla OVS: $ ./vsperf --conf-file<path_to_custom_conf>/10_custom.conf +.. _vpp-test: + +Executing VPP tests +^^^^^^^^^^^^^^^^^^^ + +Currently it is not possible to use standard scenario deployments for execution of +tests with VPP. It means, that deployments ``p2p``, ``pvp``, ``pvvp`` and in general any +:ref:`pxp-deployment` won't work with VPP. However it is possible to use VPP in +:ref:`step-driven-tests`. A basic set of VPP testcases covering ``phy2phy``, ``pvp`` +and ``pvvp`` tests are already prepared. + +List of performance tests with VPP support follows: + +* phy2phy_tput_vpp: VPP: LTD.Throughput.RFC2544.PacketLossRatio +* phy2phy_cont_vpp: VPP: Phy2Phy Continuous Stream +* phy2phy_back2back_vpp: VPP: LTD.Throughput.RFC2544.BackToBackFrames +* pvp_tput_vpp: VPP: LTD.Throughput.RFC2544.PacketLossRatio +* pvp_cont_vpp: VPP: PVP Continuous Stream +* pvp_back2back_vpp: VPP: LTD.Throughput.RFC2544.BackToBackFrames +* pvvp_tput_vpp: VPP: LTD.Throughput.RFC2544.PacketLossRatio +* pvvp_cont_vpp: VPP: PVP Continuous Stream +* pvvp_back2back_vpp: VPP: LTD.Throughput.RFC2544.BackToBackFrames + +In order to execute testcases with VPP it is required to: + +* install VPP manually, see :ref:`vpp-installation` +* configure ``WHITELIST_NICS``, with two physical NICs connected to the traffic generator +* configure traffic generator, see :ref:`trafficgen-installation` + +After that it is possible to execute VPP testcases listed above. + +For example: + +.. code-block:: console + + $ ./vsperf --conf-file=<path_to_custom_conf> phy2phy_tput_vpp + .. _vfio-pci: Using vfio_pci with DPDK @@ -704,7 +726,8 @@ application to use the correct number of nb-cores. .. code-block:: python - VSWITCHD_DPDK_ARGS = ['-l', '46,44,42,40,38', '-n', '4', '--socket-mem 1024,0'] + DPDK_SOCKET_MEM = ['1024', '0'] + VSWITCHD_DPDK_ARGS = ['-l', '46,44,42,40,38', '-n', '4'] TESTPMD_ARGS = ['--nb-cores=4', '--txq=1', '--rxq=1'] For guest TestPMD 3 VCpus should be assigned with the following TestPMD params. @@ -748,8 +771,7 @@ of traffic generator can be modified through ``TRAFFIC`` dictionary passed to th ``--test-params`` option. It is not needed to specify all values of ``TRAFFIC`` dictionary. It is sufficient to specify only values, which should be changed. Detailed description of ``TRAFFIC`` dictionary can be found at -`Configuration of TRAFFIC dictionary -<http://artifacts.opnfv.org/vswitchperf/docs/index.html#configuration-of-traffic-dictionary>`__ +:ref:`configuration-of-traffic-dictionary`. Example of execution of VSPERF in "trafficgen" mode: @@ -806,21 +828,21 @@ an appropriate amount of memory: .. code-block:: python - VSWITCHD_DPDK_ARGS = ['-c', '0x4', '-n', '4', '--socket-mem 1024,0'] + DPDK_SOCKET_MEM = ['1024', '0'] + VSWITCHD_DPDK_ARGS = ['-c', '0x4', '-n', '4'] VSWITCHD_DPDK_CONFIG = { 'dpdk-init' : 'true', 'dpdk-lcore-mask' : '0x4', 'dpdk-socket-mem' : '1024,0', } -Note: Option VSWITCHD_DPDK_ARGS is used for vswitchd, which supports --dpdk -parameter. In recent vswitchd versions, option VSWITCHD_DPDK_CONFIG will be -used to configure vswitchd via ovs-vsctl calls. +Note: Option ``VSWITCHD_DPDK_ARGS`` is used for vswitchd, which supports ``--dpdk`` +parameter. In recent vswitchd versions, option ``VSWITCHD_DPDK_CONFIG`` will be +used to configure vswitchd via ``ovs-vsctl`` calls. More information ^^^^^^^^^^^^^^^^ -For more information and details refer to the vSwitchPerf user guide at: -http://artifacts.opnfv.org/vswitchperf/docs/userguide/index.html +For more information and details refer to the rest of vSwitchPerfuser documentation. |