]>
Commit | Line | Data |
---|---|---|
542cc9bb TG |
1 | How to Install Open vSwitch on Linux, FreeBSD and NetBSD |
2 | ======================================================== | |
4b11d5e8 BP |
3 | |
4 | This document describes how to build and install Open vSwitch on a | |
76d5beb9 YT |
5 | generic Linux, FreeBSD, or NetBSD host. For specifics around installation |
6 | on a specific platform, please see one of these files: | |
4b11d5e8 | 7 | |
9feb1017 TG |
8 | - [INSTALL.Debian.md] |
9 | - [INSTALL.Fedora.md] | |
10 | - [INSTALL.RHEL.md] | |
11 | - [INSTALL.XenServer.md] | |
12 | - [INSTALL.NetBSD.md] | |
13 | - [INSTALL.DPDK.md] | |
4b11d5e8 BP |
14 | |
15 | Build Requirements | |
16 | ------------------ | |
17 | ||
18 | To compile the userspace programs in the Open vSwitch distribution, | |
19 | you will need the following software: | |
20 | ||
542cc9bb | 21 | - GNU make. |
4b11d5e8 | 22 | |
542cc9bb | 23 | - A C compiler, such as: |
8a6de510 | 24 | |
542cc9bb | 25 | * GCC 4.x. |
8a6de510 | 26 | |
542cc9bb TG |
27 | * Clang. Clang 3.4 and later provide useful static semantic |
28 | analysis and thread-safety checks. For Ubuntu, there are | |
29 | nightly built packages available on clang's website. | |
4b11d5e8 | 30 | |
542cc9bb TG |
31 | While OVS may be compatible with other compilers, optimal |
32 | support for atomic operations may be missing, making OVS very | |
33 | slow (see lib/ovs-atomic.h). | |
29d204ef | 34 | |
542cc9bb TG |
35 | - libssl, from OpenSSL, is optional but recommended if you plan to |
36 | connect the Open vSwitch to an OpenFlow controller. libssl is | |
37 | required to establish confidentiality and authenticity in the | |
38 | connections from an Open vSwitch to an OpenFlow controller. If | |
39 | libssl is installed, then Open vSwitch will automatically build | |
40 | with support for it. | |
4b11d5e8 | 41 | |
542cc9bb | 42 | - Python 2.x, for x >= 4. |
deb64473 | 43 | |
c6435221 BP |
44 | On Linux, you may choose to compile the kernel module that comes with |
45 | the Open vSwitch distribution or to use the kernel module built into | |
9feb1017 TG |
46 | the Linux kernel (version 3.3 or later). See the [FAQ.md] question |
47 | "What features are not available in the Open vSwitch kernel datapath that | |
c6435221 BP |
48 | ships as part of the upstream Linux kernel?" for more information on |
49 | this trade-off. You may also use the userspace-only implementation, | |
9feb1017 TG |
50 | at some cost in features and performance (see [INSTALL.userspace.md] |
51 | for details). To compile the kernel module on Linux, you must also | |
c6435221 | 52 | install the following: |
4b11d5e8 | 53 | |
9feb1017 | 54 | - A supported Linux kernel version. Please refer to [README.md] for a |
542cc9bb | 55 | list of supported versions. |
4b11d5e8 | 56 | |
542cc9bb TG |
57 | The Open vSwitch datapath requires bridging support |
58 | (CONFIG_BRIDGE) to be built as a kernel module. (This is common | |
59 | in kernels provided by Linux distributions.) The bridge module | |
60 | must not be loaded or in use. If the bridge module is running | |
61 | (check with "lsmod | grep bridge"), you must remove it ("rmmod | |
62 | bridge") before starting the datapath. | |
4b11d5e8 | 63 | |
542cc9bb TG |
64 | For optional support of ingress policing, you must enable kernel |
65 | configuration options NET_CLS_BASIC, NET_SCH_INGRESS, and | |
66 | NET_ACT_POLICE, either built-in or as modules. (NET_CLS_POLICE is | |
67 | obsolete and not needed.) | |
4b11d5e8 | 68 | |
542cc9bb TG |
69 | To use GRE tunneling on Linux 2.6.37 or newer, kernel support |
70 | for GRE demultiplexing (CONFIG_NET_IPGRE_DEMUX) must be compiled | |
71 | in or available as a module. Also, on kernels before 3.11, the | |
72 | ip_gre module, for GRE tunnels over IP (NET_IPGRE), must not be | |
73 | loaded or compiled in. | |
6f470982 | 74 | |
542cc9bb TG |
75 | To configure HTB or HFSC quality of service with Open vSwitch, |
76 | you must enable the respective configuration options. | |
c9d3af4e | 77 | |
542cc9bb TG |
78 | To use Open vSwitch support for TAP devices, you must enable |
79 | CONFIG_TUN. | |
26bb189d | 80 | |
542cc9bb TG |
81 | - To build a kernel module, you need the same version of GCC that |
82 | was used to build that kernel. | |
4b11d5e8 | 83 | |
542cc9bb TG |
84 | - A kernel build directory corresponding to the Linux kernel image |
85 | the module is to run on. Under Debian and Ubuntu, for example, | |
86 | each linux-image package containing a kernel binary has a | |
87 | corresponding linux-headers package with the required build | |
88 | infrastructure. | |
4b11d5e8 BP |
89 | |
90 | If you are working from a Git tree or snapshot (instead of from a | |
c9d3af4e BP |
91 | distribution tarball), or if you modify the Open vSwitch build system |
92 | or the database schema, you will also need the following software: | |
4b11d5e8 | 93 | |
542cc9bb | 94 | - Autoconf version 2.63 or later. |
4b11d5e8 | 95 | |
542cc9bb | 96 | - Automake version 1.10 or later. |
4b11d5e8 | 97 | |
542cc9bb | 98 | - libtool version 2.4 or later. (Older versions might work too.) |
195b5c35 | 99 | |
c9d3af4e BP |
100 | To run the unit tests, you also need: |
101 | ||
542cc9bb TG |
102 | - Perl. Version 5.10.1 is known to work. Earlier versions should |
103 | also work. | |
c9d3af4e | 104 | |
a5ae88ff AA |
105 | The ovs-vswitchd.conf.db(5) manpage will include an E-R diagram, in |
106 | formats other than plain text, only if you have the following: | |
f8d739a9 | 107 | |
542cc9bb | 108 | - "dot" from graphviz (http://www.graphviz.org/). |
f8d739a9 | 109 | |
542cc9bb TG |
110 | - Perl. Version 5.10.1 is known to work. Earlier versions should |
111 | also work. | |
c9d3af4e | 112 | |
542cc9bb | 113 | - Python 2.x, for x >= 4. |
c9d3af4e | 114 | |
f8f26e98 BP |
115 | If you are going to extensively modify Open vSwitch, please consider |
116 | installing the following to obtain better warnings: | |
117 | ||
542cc9bb TG |
118 | - "sparse" version 0.4.4 or later |
119 | (http://www.kernel.org/pub/software/devel/sparse/dist/). | |
f8f26e98 | 120 | |
542cc9bb | 121 | - GNU make. |
f8f26e98 | 122 | |
542cc9bb | 123 | - clang, version 3.4 or later |
97be1538 | 124 | |
fef5244f EJ |
125 | Also, you may find the ovs-dev script found in utilities/ovs-dev.py useful. |
126 | ||
4b11d5e8 BP |
127 | Installation Requirements |
128 | ------------------------- | |
129 | ||
130 | The machine on which Open vSwitch is to be installed must have the | |
131 | following software: | |
132 | ||
542cc9bb | 133 | - libc compatible with the libc used for build. |
4b11d5e8 | 134 | |
542cc9bb TG |
135 | - libssl compatible with the libssl used for build, if OpenSSL was |
136 | used for the build. | |
4b11d5e8 | 137 | |
542cc9bb | 138 | - On Linux, the same kernel version configured as part of the build. |
4b11d5e8 | 139 | |
542cc9bb TG |
140 | - For optional support of ingress policing on Linux, the "tc" program |
141 | from iproute2 (part of all major distributions and available at | |
142 | http://www.linux-foundation.org/en/Net:Iproute2). | |
4b11d5e8 | 143 | |
f6eb6b20 GL |
144 | On Linux you should ensure that /dev/urandom exists. To support TAP |
145 | devices, you must also ensure that /dev/net/tun exists. | |
6e8e271c | 146 | |
76d5beb9 YT |
147 | Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD |
148 | ================================================================= | |
4b11d5e8 BP |
149 | |
150 | Once you have installed all the prerequisites listed above in the Base | |
151 | Prerequisites section, follow the procedure below to build. | |
152 | ||
f6eb6b20 | 153 | 1. If you pulled the sources directly from an Open vSwitch Git tree, |
30746a1b JP |
154 | run boot.sh in the top source directory: |
155 | ||
542cc9bb | 156 | `% ./boot.sh` |
30746a1b | 157 | |
ef7889b4 BP |
158 | 2. Configure the package by running the configure script. You can |
159 | usually invoke configure without any arguments. For example: | |
4b11d5e8 | 160 | |
542cc9bb | 161 | `% ./configure` |
4b11d5e8 BP |
162 | |
163 | By default all files are installed under /usr/local. If you want | |
164 | to install into, e.g., /usr and /var instead of /usr/local and | |
165 | /usr/local/var, add options as shown here: | |
166 | ||
542cc9bb | 167 | `% ./configure --prefix=/usr --localstatedir=/var` |
4b11d5e8 BP |
168 | |
169 | To use a specific C compiler for compiling Open vSwitch user | |
170 | programs, also specify it on the configure command line, like so: | |
171 | ||
542cc9bb | 172 | `% ./configure CC=gcc-4.2` |
4b11d5e8 | 173 | |
97be1538 EJ |
174 | To use 'clang' compiler: |
175 | ||
542cc9bb | 176 | `% ./configure CC=clang` |
97be1538 | 177 | |
4b11d5e8 BP |
178 | To build the Linux kernel module, so that you can run the |
179 | kernel-based switch, pass the location of the kernel build | |
338fb44a | 180 | directory on --with-linux. For example, to build for a running |
8a2d6596 | 181 | instance of Linux: |
4b11d5e8 | 182 | |
542cc9bb | 183 | `% ./configure --with-linux=/lib/modules/`uname -r`/build` |
4b11d5e8 | 184 | |
a7ae9380 BP |
185 | If --with-linux requests building for an unsupported version of |
186 | Linux, then "configure" will fail with an error message. Please | |
9feb1017 | 187 | refer to the [FAQ.md] for advice in that case. |
a7ae9380 | 188 | |
4b11d5e8 BP |
189 | If you wish to build the kernel module for an architecture other |
190 | than the architecture of the machine used for the build, you may | |
191 | specify the kernel architecture string using the KARCH variable | |
192 | when invoking the configure script. For example, to build for MIPS | |
8a2d6596 | 193 | with Linux: |
4b11d5e8 | 194 | |
542cc9bb | 195 | `% ./configure --with-linux=/path/to/linux KARCH=mips` |
4b11d5e8 | 196 | |
ad367b28 BP |
197 | If you plan to do much Open vSwitch development, you might want to |
198 | add --enable-Werror, which adds the -Werror option to the compiler | |
199 | command line, turning warnings into errors. That makes it | |
200 | impossible to miss warnings generated by the build. | |
201 | ||
e3c7ed29 BP |
202 | To build with gcov code coverage support, add --enable-coverage, |
203 | e.g.: | |
204 | ||
542cc9bb | 205 | `% ./configure --enable-coverage` |
e3c7ed29 | 206 | |
4b11d5e8 BP |
207 | The configure script accepts a number of other options and honors |
208 | additional environment variables. For a full list, invoke | |
209 | configure with the --help option. | |
210 | ||
ef7889b4 BP |
211 | You can also run configure from a separate build directory. This |
212 | is helpful if you want to build Open vSwitch in more than one way | |
213 | from a single source directory, e.g. to try out both GCC and Clang | |
214 | builds, or to build kernel modules for more than one Linux version. | |
215 | Here is an example: | |
216 | ||
542cc9bb TG |
217 | `% mkdir _gcc && (cd _gcc && ../configure CC=gcc)` |
218 | `% mkdir _clang && (cd _clang && ../configure CC=clang)` | |
ef7889b4 BP |
219 | |
220 | 3. Run GNU make in the build directory, e.g.: | |
4b11d5e8 | 221 | |
542cc9bb | 222 | `% make` |
4b11d5e8 | 223 | |
380b39f7 BP |
224 | or if GNU make is installed as "gmake": |
225 | ||
542cc9bb | 226 | `% gmake` |
f6eb6b20 | 227 | |
ef7889b4 BP |
228 | If you used a separate build directory, run make or gmake from that |
229 | directory, e.g.: | |
230 | ||
542cc9bb TG |
231 | `% make -C _gcc` |
232 | `% make -C _clang` | |
ef7889b4 | 233 | |
f8f26e98 | 234 | For improved warnings if you installed "sparse" (see |
380b39f7 | 235 | "Prerequisites"), add C=1 to the command line. |
f8f26e98 | 236 | |
875ef81b KM |
237 | 4. Consider running the testsuite. Refer to "Running the Testsuite" |
238 | below, for instructions. | |
4b11d5e8 | 239 | |
875ef81b KM |
240 | 5. Become root by running "su" or another program. |
241 | ||
242 | 6. Run "make install" to install the executables and manpages into the | |
4b11d5e8 BP |
243 | running system, by default under /usr/local. |
244 | ||
ffd6065a | 245 | 7. If you built kernel modules, you may install and load them, e.g.: |
4b11d5e8 | 246 | |
542cc9bb TG |
247 | `% make modules_install` |
248 | `% /sbin/modprobe openvswitch` | |
4b11d5e8 | 249 | |
4b11d5e8 | 250 | To verify that the modules have been loaded, run "/sbin/lsmod" and |
9b80f761 | 251 | check that openvswitch is listed. |
4b11d5e8 | 252 | |
542cc9bb TG |
253 | If the `modprobe` operation fails, look at the last few kernel log |
254 | messages (e.g. with `dmesg | tail`): | |
dd2d79ce | 255 | |
9b80f761 | 256 | - The message "openvswitch: exports duplicate symbol |
dd2d79ce | 257 | br_should_route_hook (owned by bridge)" means that the bridge |
542cc9bb | 258 | module is loaded. Run `/sbin/rmmod bridge` to remove it. |
dd2d79ce | 259 | |
542cc9bb | 260 | If `/sbin/rmmod bridge` fails with "ERROR: Module bridge does |
dd2d79ce BP |
261 | not exist in /proc/modules", then the bridge is compiled into |
262 | the kernel, rather than as a module. Open vSwitch does not | |
263 | support this configuration (see "Build Requirements", above). | |
264 | ||
9b80f761 | 265 | - The message "openvswitch: exports duplicate symbol |
dd2d79ce BP |
266 | dp_ioctl_hook (owned by ofdatapath)" means that the ofdatapath |
267 | module from the OpenFlow reference implementation is loaded. | |
542cc9bb | 268 | Run `/sbin/rmmod ofdatapath` to remove it. (You might have to |
dd2d79ce BP |
269 | delete any existing datapaths beforehand, using the "dpctl" |
270 | program included with the OpenFlow reference implementation. | |
271 | "ovs-dpctl" will not work.) | |
272 | ||
273 | - Otherwise, the most likely problem is that Open vSwitch was | |
274 | built for a kernel different from the one into which you are | |
542cc9bb | 275 | trying to load it. Run `modinfo` on openvswitch.ko and on |
dd2d79ce BP |
276 | a module built for the running kernel, e.g.: |
277 | ||
542cc9bb | 278 | ``` |
9b80f761 | 279 | % /sbin/modinfo openvswitch.ko |
dd2d79ce | 280 | % /sbin/modinfo /lib/modules/`uname -r`/kernel/net/bridge/bridge.ko |
542cc9bb | 281 | ``` |
dd2d79ce BP |
282 | |
283 | Compare the "vermagic" lines output by the two commands. If | |
284 | they differ, then Open vSwitch was built for the wrong kernel. | |
285 | ||
286 | - If you decide to report a bug or ask a question related to | |
542cc9bb TG |
287 | module loading, please include the output from the `dmesg` and |
288 | `modinfo` commands mentioned above. | |
dd2d79ce | 289 | |
9b80f761 | 290 | There is an optional module parameter to openvswitch.ko called |
3f6256af JG |
291 | vlan_tso that enables TCP segmentation offload over VLANs on NICs |
292 | that support it. Many drivers do not expose support for TSO on VLANs | |
293 | in a way that Open vSwitch can use but there is no way to detect | |
294 | whether this is the case. If you know that your particular driver can | |
295 | handle it (for example by testing sending large TCP packets over VLANs) | |
296 | then passing in a value of 1 may improve performance. Modules built for | |
431488e6 BP |
297 | Linux kernels 2.6.37 and later, as well as specially patched versions |
298 | of earlier kernels, do not need this and do not have this parameter. If | |
299 | you do not understand what this means or do not know if your driver | |
300 | will work, do not set this. | |
3f6256af | 301 | |
875ef81b | 302 | 8. Initialize the configuration database using ovsdb-tool, e.g.: |
4b11d5e8 | 303 | |
542cc9bb TG |
304 | `% mkdir -p /usr/local/etc/openvswitch` |
305 | `% ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema` | |
4b11d5e8 | 306 | |
3b12adda BP |
307 | Startup |
308 | ======= | |
4b11d5e8 | 309 | |
3b12adda | 310 | Before starting ovs-vswitchd itself, you need to start its |
cb8141b2 BP |
311 | configuration database, ovsdb-server. Each machine on which Open |
312 | vSwitch is installed should run its own copy of ovsdb-server. | |
566b8c8d BP |
313 | Configure it to use the database you created during installation (as |
314 | explained above), to listen on a Unix domain socket, to connect to any | |
315 | managers specified in the database itself, and to use the SSL | |
8084a280 BP |
316 | configuration in the database: |
317 | ||
29701194 | 318 | % ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock \ |
6faab099 JP |
319 | --remote=db:Open_vSwitch,Open_vSwitch,manager_options \ |
320 | --private-key=db:Open_vSwitch,SSL,private_key \ | |
321 | --certificate=db:Open_vSwitch,SSL,certificate \ | |
322 | --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert \ | |
29701194 | 323 | --pidfile --detach |
3b12adda | 324 | |
d3e3fb58 BP |
325 | (If you built Open vSwitch without SSL support, then omit |
326 | --private-key, --certificate, and --bootstrap-ca-cert.) | |
327 | ||
de4f3c10 | 328 | Then initialize the database using ovs-vsctl. This is only |
332b4e09 BP |
329 | necessary the first time after you create the database with |
330 | ovsdb-tool (but running it at any time is harmless): | |
331 | ||
de4f3c10 | 332 | % ovs-vsctl --no-wait init |
332b4e09 | 333 | |
3b12adda BP |
334 | Then start the main Open vSwitch daemon, telling it to connect to the |
335 | same Unix domain socket: | |
336 | ||
80df177a | 337 | % ovs-vswitchd --pidfile --detach |
3b12adda BP |
338 | |
339 | Now you may use ovs-vsctl to set up bridges and other Open vSwitch | |
340 | features. For example, to create a bridge named br0 and add ports | |
341 | eth0 and vif1.0 to it: | |
342 | ||
343 | % ovs-vsctl add-br br0 | |
344 | % ovs-vsctl add-port br0 eth0 | |
345 | % ovs-vsctl add-port br0 vif1.0 | |
346 | ||
347 | Please refer to ovs-vsctl(8) for more details. | |
4b11d5e8 | 348 | |
8b055d92 BP |
349 | Upgrading |
350 | ========= | |
351 | ||
352 | When you upgrade Open vSwitch from one version to another, you should | |
353 | also upgrade the database schema: | |
354 | ||
355 | 1. Stop the Open vSwitch daemons, e.g.: | |
356 | ||
542cc9bb | 357 | ``` |
012f5c4b | 358 | % kill `cd /usr/local/var/run/openvswitch && cat ovsdb-server.pid ovs-vswitchd.pid` |
542cc9bb | 359 | ``` |
8b055d92 BP |
360 | |
361 | 2. Install the new Open vSwitch release. | |
362 | ||
363 | 3. Upgrade the database, in one of the following two ways: | |
364 | ||
365 | - If there is no important data in your database, then you may | |
366 | delete the database file and recreate it with ovsdb-tool, | |
367 | following the instructions under "Building and Installing Open | |
76d5beb9 | 368 | vSwitch for Linux, FreeBSD or NetBSD". |
8b055d92 BP |
369 | |
370 | - If you want to preserve the contents of your database, back it | |
371 | up first, then use "ovsdb-tool convert" to upgrade it, e.g.: | |
372 | ||
542cc9bb | 373 | `% ovsdb-tool convert /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema` |
8b055d92 BP |
374 | |
375 | 4. Start the Open vSwitch daemons as described under "Building and | |
76d5beb9 | 376 | Installing Open vSwitch for Linux, FreeBSD or NetBSD" above. |
8b055d92 | 377 | |
4e375050 GS |
378 | Hot Upgrading |
379 | ============= | |
380 | Upgrading Open vSwitch from one version to the next version with minimum | |
381 | disruption of traffic going through the system that is using that Open vSwitch | |
382 | needs some considerations: | |
383 | ||
384 | 1. If the upgrade only involves upgrading the userspace utilities and daemons | |
385 | of Open vSwitch, make sure that the new userspace version is compatible with | |
386 | the previously loaded kernel module. | |
387 | ||
388 | 2. An upgrade of userspace daemons means that they have to be restarted. | |
ea274df9 | 389 | Restarting the daemons means that the OpenFlow flows in the ovs-vswitchd daemon |
4e375050 GS |
390 | will be lost. One way to restore the flows is to let the controller |
391 | re-populate it. Another way is to save the previous flows using a utility | |
392 | like ovs-ofctl and then re-add them after the restart. Restoring the old flows | |
393 | is accurate only if the new Open vSwitch interfaces retain the old 'ofport' | |
394 | values. | |
395 | ||
396 | 3. When the new userspace daemons get restarted, they automatically flush | |
397 | the old flows setup in the kernel. This can be expensive if there are hundreds | |
398 | of new flows that are entering the kernel but userspace daemons are busy | |
399 | setting up new userspace flows from either the controller or an utility like | |
400 | ovs-ofctl. Open vSwitch database provides an option to solve this problem | |
401 | through the other_config:flow-restore-wait column of the Open_vSwitch table. | |
402 | Refer to the ovs-vswitchd.conf.db(5) manpage for details. | |
403 | ||
404 | 4. If the upgrade also involves upgrading the kernel module, the old kernel | |
405 | module needs to be unloaded and the new kernel module should be loaded. This | |
406 | means that the kernel network devices belonging to Open vSwitch is recreated | |
407 | and the kernel flows are lost. The downtime of the traffic can be reduced | |
408 | if the userspace daemons are restarted immediately and the userspace flows | |
409 | are restored as soon as possible. | |
410 | ||
411 | The ovs-ctl utility's "restart" function only restarts the userspace daemons, | |
412 | makes sure that the 'ofport' values remain consistent across restarts, restores | |
413 | userspace flows using the ovs-ofctl utility and also uses the | |
414 | other_config:flow-restore-wait column to keep the traffic downtime to the | |
415 | minimum. The ovs-ctl utility's "force-reload-kmod" function does all of the | |
416 | above, but also replaces the old kernel module with the new one. Open vSwitch | |
417 | startup scripts for Debian, XenServer and RHEL use ovs-ctl's functions and it | |
418 | is recommended that these functions be used for other software platforms too. | |
419 | ||
e3c7ed29 BP |
420 | Testsuites |
421 | ========== | |
422 | ||
423 | This section describe Open vSwitch's built-in support for various test | |
424 | suites. You must configure and build Open vSwitch (steps 1 through 3 | |
425 | in "Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD" | |
426 | above) before you run the tests described here. You do not need to | |
427 | install Open vSwitch or to build or load the kernel module to run | |
428 | these test suites. You do not need supervisor privilege to run these | |
429 | test suites. | |
875ef81b | 430 | |
e3c7ed29 BP |
431 | Self-Tests |
432 | ---------- | |
433 | ||
434 | Open vSwitch includes a suite of self-tests. Before you submit patches | |
875ef81b KM |
435 | upstream, we advise that you run the tests and ensure that they pass. |
436 | If you add new features to Open vSwitch, then adding tests for those | |
437 | features will ensure your features don't break as developers modify | |
438 | other areas of Open vSwitch. | |
439 | ||
e3c7ed29 | 440 | Refer to "Testsuites" above for prerequisites. |
875ef81b KM |
441 | |
442 | To run all the unit tests in Open vSwitch, one at a time: | |
542cc9bb | 443 | `make check` |
875ef81b KM |
444 | This takes under 5 minutes on a modern desktop system. |
445 | ||
446 | To run all the unit tests in Open vSwitch, up to 8 in parallel: | |
542cc9bb | 447 | `make check TESTSUITEFLAGS=-j8` |
875ef81b KM |
448 | This takes under a minute on a modern 4-core desktop system. |
449 | ||
450 | To see a list of all the available tests, run: | |
542cc9bb | 451 | `make check TESTSUITEFLAGS=--list` |
875ef81b KM |
452 | |
453 | To run only a subset of tests, e.g. test 123 and tests 477 through 484: | |
542cc9bb | 454 | `make check TESTSUITEFLAGS='123 477-484'` |
875ef81b KM |
455 | (Tests do not have inter-dependencies, so you may run any subset.) |
456 | ||
457 | To run tests matching a keyword, e.g. "ovsdb": | |
542cc9bb | 458 | `make check TESTSUITEFLAGS='-k ovsdb'` |
875ef81b KM |
459 | |
460 | To see a complete list of test options: | |
542cc9bb | 461 | `make check TESTSUITEFLAGS=--help` |
875ef81b KM |
462 | |
463 | The results of a testing run are reported in tests/testsuite.log. | |
464 | Please report test failures as bugs and include the testsuite.log in | |
465 | your report. | |
466 | ||
467 | If you have "valgrind" installed, then you can also run the testsuite | |
468 | under valgrind by using "make check-valgrind" in place of "make | |
469 | check". All the same options are available via TESTSUITEFLAGS. When | |
542cc9bb TG |
470 | you do this, the "valgrind" results for test `<N>` are reported in files |
471 | named `tests/testsuite.dir/<N>/valgrind.*`. You may find that the | |
875ef81b | 472 | valgrind results are easier to interpret if you put "-q" in |
447fe5cf | 473 | ~/.valgrindrc, since that reduces the amount of output. |
875ef81b KM |
474 | |
475 | Sometimes a few tests may fail on some runs but not others. This is | |
476 | usually a bug in the testsuite, not a bug in Open vSwitch itself. If | |
477 | you find that a test fails intermittently, please report it, since the | |
478 | developers may not have noticed. | |
479 | ||
e3c7ed29 BP |
480 | OFTest |
481 | ------ | |
482 | ||
483 | OFTest is an OpenFlow protocol testing suite. Open vSwitch includes a | |
484 | Makefile target to run OFTest with Open vSwitch in "dummy mode". In | |
485 | this mode of testing, no packets travel across physical or virtual | |
486 | networks. Instead, Unix domain sockets stand in as simulated | |
487 | networks. This simulation is imperfect, but it is much easier to set | |
488 | up, does not require extra physical or virtual hardware, and does not | |
489 | require supervisor privileges. | |
490 | ||
491 | To run OFTest with Open vSwitch, first read and follow the | |
492 | instructions under "Testsuites" above. Second, obtain a copy of | |
493 | OFTest and install its prerequisites. You need a copy of OFTest that | |
494 | includes commit 406614846c5 (make ovs-dummy platform work again). | |
495 | This commit was merged into the OFTest repository on Feb 1, 2013, so | |
496 | any copy of OFTest more recent than that should work. Testing OVS in | |
497 | dummy mode does not require root privilege, so you may ignore that | |
498 | requirement. | |
499 | ||
500 | Optionally, add the top-level OFTest directory (containing the "oft" | |
501 | program) to your $PATH. This slightly simplifies running OFTest later. | |
502 | ||
503 | To run OFTest in dummy mode, run the following command from your Open | |
504 | vSwitch build directory: | |
542cc9bb TG |
505 | `make check-oftest OFT=<oft-binary>` |
506 | where `<oft-binary>` is the absolute path to the "oft" program in | |
e3c7ed29 BP |
507 | OFTest. |
508 | ||
509 | If you added "oft" to your $PATH, you may omit the OFT variable | |
510 | assignment: | |
542cc9bb | 511 | `make check-oftest` |
e3c7ed29 BP |
512 | By default, "check-oftest" passes "oft" just enough options to enable |
513 | dummy mode. You can use OFTFLAGS to pass additional options. For | |
514 | example, to run just the basic.Echo test instead of all tests (the | |
515 | default) and enable verbose logging: | |
542cc9bb | 516 | `make check-oftest OFT=<oft-binary> OFTFLAGS='--verbose -T basic.Echo'` |
e3c7ed29 BP |
517 | |
518 | If you use OFTest that does not include commit 4d1f3eb2c792 (oft: | |
519 | change default port to 6653), merged into the OFTest repository in | |
520 | October 2013, then you need to add an option to use the IETF-assigned | |
521 | controller port: | |
542cc9bb | 522 | `make check-oftest OFT=<oft-binary> OFTFLAGS='--port=6653'` |
e3c7ed29 BP |
523 | |
524 | Please interpret OFTest results cautiously. Open vSwitch can fail a | |
525 | given test in OFTest for many reasons, including bugs in Open vSwitch, | |
526 | bugs in OFTest, bugs in the "dummy mode" integration, and differing | |
527 | interpretations of the OpenFlow standard and other standards. | |
528 | ||
529 | Open vSwitch has not been validated against OFTest. Please do report | |
530 | test failures that you believe to represent bugs in Open vSwitch. | |
531 | Include the precise versions of Open vSwitch and OFTest in your bug | |
532 | report, plus any other information needed to reproduce the problem. | |
533 | ||
534 | Ryu | |
535 | --- | |
536 | ||
537 | Ryu is an OpenFlow controller written in Python that includes an | |
538 | extensive OpenFlow testsuite. Open vSwitch includes a Makefile target | |
539 | to run Ryu in "dummy mode". See "OFTest" above for an explanation of | |
540 | dummy mode. | |
541 | ||
542 | To run Ryu tests with Open vSwitch, first read and follow the | |
543 | instructions under "Testsuites" above. Second, obtain a copy of Ryu, | |
544 | install its prerequisites, and build it. You do not need to install | |
545 | Ryu (some of the tests do not get installed, so it does not help). | |
546 | ||
547 | To run Ryu tests, run the following command from your Open vSwitch | |
548 | build directory: | |
542cc9bb TG |
549 | `make check-ryu RYUDIR=<ryu-source-dir>` |
550 | where `<ryu-source-dir>` is the absolute path to the root of the Ryu | |
551 | source distribution. The default `<ryu-source-dir>` is `$srcdir/../ryu` | |
e3c7ed29 | 552 | where $srcdir is your Open vSwitch source directory, so if this |
542cc9bb | 553 | default is correct then you make simply run `make check-ryu`. |
e3c7ed29 BP |
554 | |
555 | Open vSwitch has not been validated against Ryu. Please do report | |
556 | test failures that you believe to represent bugs in Open vSwitch. | |
557 | Include the precise versions of Open vSwitch and Ryu in your bug | |
558 | report, plus any other information needed to reproduce the problem. | |
559 | ||
8187f55b TG |
560 | Continuous Integration with Travis-CI |
561 | ------------------------------------- | |
562 | ||
563 | A .travis.yml file is provided to automatically build Open vSwitch with | |
564 | various build configurations and run the testsuite using travis-ci. | |
565 | Builds will be performed with gcc, sparse and clang with the -Werror | |
566 | compiler flag included, therefore the build will fail if a new warning | |
567 | has been introduced. | |
568 | ||
569 | The CI build is triggered via git push (regardless of the specific | |
570 | branch) or pull request against any Open vSwitch GitHub repository that | |
571 | is linked to travis-ci. | |
572 | ||
573 | Instructions to setup travis-ci for your GitHub repository: | |
574 | ||
35ab726f | 575 | 1. Go to http://travis-ci.org/ and sign in using your GitHub ID. |
8187f55b TG |
576 | 2. Go to the "Repositories" tab and enable the ovs repository. You |
577 | may disable builds for pushes or pull requests. | |
578 | 3. In order to avoid forks sending build failures to the upstream | |
579 | mailing list, the notification email recipient is encrypted. If you | |
580 | want to receive email notification for build failures, replace the | |
581 | the encrypted string: | |
582 | 3.1) Install the travis-ci CLI (Requires ruby >=2.0): | |
583 | gem install travis | |
584 | 3.2) In your Open vSwitch repository: | |
585 | travis encrypt mylist@mydomain.org | |
586 | 3.3) Add/replace the notifications section in .travis.yml and fill | |
587 | in the secure string as returned by travis encrypt: | |
588 | ||
589 | notifications: | |
590 | email: | |
591 | recipients: | |
592 | - secure: "....." | |
593 | ||
594 | (You may remove/omit the notifications section to fall back to | |
595 | default notification behaviour which is to send an email directly | |
596 | to the author and committer of the failing commit. Note that the | |
597 | email is only sent if the author/committer have commit rights for | |
598 | the particular GitHub repository). | |
599 | ||
600 | 4. Pushing a commit to the repository which breaks the build or the | |
601 | testsuite will now trigger a email sent to mylist@mydomain.org | |
602 | ||
4b11d5e8 | 603 | Bug Reporting |
e3c7ed29 | 604 | ============= |
4b11d5e8 | 605 | |
37ea6436 | 606 | Please report problems to bugs@openvswitch.org. |
9feb1017 TG |
607 | |
608 | [README.md]:README.md | |
609 | [INSTALL.Debian.md]:INSTALL.Debian.md | |
610 | [INSTALL.Fedora.md]:INSTALL.Fedora.md | |
611 | [INSTALL.RHEL.md]:INSTALL.RHEL.md | |
612 | [INSTALL.XenServer.md]:INSTALL.XenServer.md | |
613 | [INSTALL.NetBSD.md]:INSTALL.NetBSD.md | |
614 | [INSTALL.DPDK.md]:INSTALL.DPDK.md | |
615 | [INSTALL.userspace.md]:INSTALL.userspace.md | |
616 | [FAQ.md]:FAQ.md |