User Tools

Site Tools


get_started:pod_3_-_characterize_vswitch_performance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
get_started:pod_3_-_characterize_vswitch_performance [2015/10/07 14:44]
Billy O'Mahony [Overview]
get_started:pod_3_-_characterize_vswitch_performance [2016/01/18 11:13] (current)
Maryam Tahhan [***NOTICE***]
Line 1: Line 1:
 +====== ***NOTICE*** ======
 +**POD 3 is now used for vsperf CI support, it runs the daily jobs and commit gate validation. As such __IT IS NOT RECOMMENDED TO USE POD 3 AS A SANDBOX AT THIS TIME__. Efforts are being undertaken to setup another sandbox environment for VSPERF. Feel free to follow the example connections and configurations shown below in your own environment.**
 +
 ====== Overview ====== ====== Overview ======
 Testbed **POD3** is available for OPNFV community to test and develop vswitchperf. In general, the testing environment consists of an IXIA traffic generator and linux machine (referred to as DUT) dedicated for vswitchperf test suite and its dependencies. Testbed **POD3** is available for OPNFV community to test and develop vswitchperf. In general, the testing environment consists of an IXIA traffic generator and linux machine (referred to as DUT) dedicated for vswitchperf test suite and its dependencies.
  
-The testbed can be accessed over OpenVPN connection, after required certificates are assigned and delivered to interested //​OPNFV ​contributer// by contacting ''​opnfv-helpdesk@rt.linuxfoundation.org''​+The testbed can be accessed over OpenVPN connection, after required certificates are assigned and delivered to interested //​OPNFV ​member//. See below for contact details.
  
 There are multiple machines at POD3 setup, but for vswitchperf testing the following two are important: There are multiple machines at POD3 setup, but for vswitchperf testing the following two are important:
Line 9: Line 12:
 ^ Server role                  ^ IP        ^ Server OS       ^ Access credentials ​                                                       ^ Access method ​                                                               ^ ^ Server role                  ^ IP        ^ Server OS       ^ Access credentials ​                                                       ^ Access method ​                                                               ^
 | DUT/​testbed ​                 | 10.4.2.1 ​ | Linux Centos7 ​  | user/​user ​                                                                | ssh, e.g. <​code>​ssh user@10.4.2.1</​code> ​                                    | | DUT/​testbed ​                 | 10.4.2.1 ​ | Linux Centos7 ​  | user/​user ​                                                                | ssh, e.g. <​code>​ssh user@10.4.2.1</​code> ​                                    |
-Ixia Windows Client ​         | 10.4.2.0 ​ | Windows 8 (VM)  | administrator/​P@ssw0rd ​                                                   | rdesktop, e.g. <​code>​rdesktop -u administrator -g 1024x1024 10.4.2.0</​code> ​ |+Traffic Gen Windows Client ​         | 10.4.2.0 ​ | Windows 8 (VM)  | administrator/​P@ssw0rd ​                                                   | rdesktop, e.g. <​code>​rdesktop -u administrator -g 1024x1024 10.4.2.0</​code> ​ |
 | Traffic Gen Server/​testbed2 ​ | 10.4.2.4 ​ | Linux Centos7 ​  | non-root account with sudo privileges. Username: opnfv Password: octopus ​ | ssh, e.g. <​code>​ssh opnfv@10.4.2.4</​code> ​                                   | | Traffic Gen Server/​testbed2 ​ | 10.4.2.4 ​ | Linux Centos7 ​  | non-root account with sudo privileges. Username: opnfv Password: octopus ​ | ssh, e.g. <​code>​ssh opnfv@10.4.2.4</​code> ​                                   |
  
Line 17: Line 20:
  
  
-**Please check** [[get_started:​intel_hosting]] **page for details about OpenVPN setup and POD3 testbed details.** **In case you need credentials for OpenVPN access to POD testbedsyou could contact ​Michael Wynne** <michaelx.s.wynne@intel.com>​+**Please check** [[get_started:​intel_hosting]] **page for details about OpenVPN setup and POD3 testbed details.** **In case you need credentials for OpenVPN access to POD3, contact ​Jack Morgan** <Jack Morgan@intel.com>​
  
 ====== POD 3 Booking Calendar ====== ====== POD 3 Booking Calendar ======
Line 33: Line 36:
 ens513f1: ether 00:​1e:​67:​e2:​67:​e1 --> connected to --> ens2f1: ether 90:​e2:​ba:​4a:​7f:​b1 ens513f1: ether 00:​1e:​67:​e2:​67:​e1 --> connected to --> ens2f1: ether 90:​e2:​ba:​4a:​7f:​b1
 ====== Usage ====== ====== Usage ======
-==== Ixia Windows Client ==== +==== Ixia on Traffic Gen Windows Client ==== 
-It is essential, that IxNetwork TCL server is up and running (at port 9111) at IXIA Windows Client machine 10.4.2.0. Otherwise vswitchperf won't be able to initiate traffic generation and tests will fail. So before testing itself, following steps must be performed:+It is essential, that IxNetwork TCL server is up and running (at port 9111) at Traffic Gen Windows Client machine 10.4.2.0. Otherwise vswitchperf won't be able to initiate traffic generation and tests will fail. So before testing itself, following steps must be performed:
   - login to the machine with remote desktop, e.g. <​code>​rdesktop -u administrator -g 1024x1024 10.4.2.0</​code>​   - login to the machine with remote desktop, e.g. <​code>​rdesktop -u administrator -g 1024x1024 10.4.2.0</​code>​
   - check if IxNetwork is running - if so, there will be an **Nw** icon in the system tray   - check if IxNetwork is running - if so, there will be an **Nw** icon in the system tray
Line 122: Line 125:
     TRAFFICGEN_IXNET_TESTER_RESULT_DIR = '​c:/​temp/​ixia'​     TRAFFICGEN_IXNET_TESTER_RESULT_DIR = '​c:/​temp/​ixia'​
     TRAFFICGEN_IXNET_DUT_RESULT_DIR = '/​mnt/​ixia'​     TRAFFICGEN_IXNET_DUT_RESULT_DIR = '/​mnt/​ixia'​
 +    ​
 +    VSWITCH_VANILLA_PHY_PORT_NAMES = ['​enp5s0f0',​ '​enp5s0f1'​]
 +    VANILLA_NIC1_NAME = ['​eth1',​ '​eth3'​]
 +    VANILLA_NIC2_NAME = ['​eth2',​ '​eth4'​]
     ​     ​
     TEST_PARAMS = {'​packet_sizes':'​64'​}</​code>​     TEST_PARAMS = {'​packet_sizes':'​64'​}</​code>​
Line 176: Line 183:
  
 # standard prompt for guest image # standard prompt for guest image
-GUEST_PROMPT = '​root@ovdk_guest ​~]#'+GUEST_PROMPT = '​root@ovdk_guest ​.*]#'
  
 # log file for qemu # log file for qemu
Line 189: Line 196:
 # ############################​ # ############################​
 QEMU_BIN = '/​home/​user/​vswitchperf/​src/​qemu/​qemu/​x86_64-softmmu/​qemu-system-x86_64'​ QEMU_BIN = '/​home/​user/​vswitchperf/​src/​qemu/​qemu/​x86_64-softmmu/​qemu-system-x86_64'​
- 
-# Guest shell prompt when inside DPDK dir 
-# for example: root@ovdk_guest DPDK]#'​ 
-QEMU_GUEST_DPDK_PROMPT = '​root@ovdk_guest DPDK]#'​ 
- 
-# Guest shell prompt when inside the 
-# test-pmd directory of DPDK 
-# for example: '​root@ovdk_guest test-pmd]#'​ 
-QEMU_GUEST_TEST_PMD_PROMPT = '​root@ovdk_guest test-pmd]#'​ 
  
 OVS_VAR_DIR = '/​usr/​local/​var/​run/​openvswitch/'​ OVS_VAR_DIR = '/​usr/​local/​var/​run/​openvswitch/'​
Line 205: Line 203:
  
 GUEST_NET1_PCI_ADDRESS = '​00:​04.0'​ GUEST_NET1_PCI_ADDRESS = '​00:​04.0'​
-GUEST_NET2_PCI_ADDRESS = '​00:​05.0'</​code>​+GUEST_NET2_PCI_ADDRESS = '​00:​05.0'​ 
 +</​code>​
  
 Run the test: Run the test:
  <​code>​./​vsperf -t pvp_tput</​code>​  <​code>​./​vsperf -t pvp_tput</​code>​
get_started/pod_3_-_characterize_vswitch_performance.1444229070.txt.gz · Last modified: 2015/10/07 14:44 by Billy O'Mahony