blob: abd09cb4b8c59ba5be46646eb42a7ce7737a5e98 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
======================
Installing vswitchperf
======================
The test suite requires Python 3.3 and relies on a number of other
packages. These need to be installed for the test suite to function.
Installation of required packages, preparation of Python 3 virtual
environment and compilation of OVS, DPDK and QEMU is performed by
script **systems/build_base_machine.sh**. It should be executed under
user account, which will be used for vsperf execution.
Please Note: Password-less sudo access must be configured for given
user account before script is executed.
Execution of installation script:
.. code:: bash
$ cd systems
$ ./build_base_machine.sh
Please note: you don't need to go into any of the systems subdirectories,
simply run the top level **build_base_machine.sh**, your OS will be detected
automatically.
Currently supported operating systems are:
- CentOS 7
- Fedora 20
- Fedora 21
- Fedora 22
- Ubuntu 14.04
Script **build_base_machine.sh** will install all the vsperf dependencies
in terms of system packages, Python 3.x and required Python modules.
In case of CentOS 7 it will install Python 3.3 from an additional repository
provided by Software Collections (`a link`_). Installation script will also
use `virtualenv`_ to create a vsperf virtual environment, which is isolated
from the default Python environment. This environment will reside
in a directory called **vsperfenv** in $HOME.
You will need to activate the virtual environment every time you start a
new shell session. Its activation is specific to your OS:
CentOS 7:
.. code:: bash
$ scl enable python33 bash
$ cd $HOME/vsperfenv
$ source bin/activate
Fedora and Ubuntu:
.. code:: bash
$ cd $HOME/vsperfenv
$ source bin/activate
--------------
Working Behind a Proxy
======================
If you're behind a proxy, you'll likely want to configure this before
running any of the above. For example:
.. code:: bash
export http_proxy=proxy.mycompany.com:123
export https_proxy=proxy.mycompany.com:123
.. _a link: http://www.softwarecollections.org/en/scls/rhscl/python33/
.. _virtualenv: https://virtualenv.readthedocs.org/en/latest/
|
