1 How to Install Open vSwitch on Linux, FreeBSD and NetBSD
2 ========================================================
4 This document describes how to build and install Open vSwitch on a
5 generic Linux, FreeBSD, or NetBSD host. For specifics around installation
6 on a specific platform, please see one of these files:
11 - [INSTALL.XenServer.md]
13 - [INSTALL.Windows.md]
19 To compile the userspace programs in the Open vSwitch distribution,
20 you will need the following software:
24 - A C compiler, such as:
28 * Clang. Clang 3.4 and later provide useful static semantic
29 analysis and thread-safety checks. For Ubuntu, there are
30 nightly built packages available on clang's website.
32 * MSVC 2013. See [INSTALL.Windows] for additional Windows build
35 While OVS may be compatible with other compilers, optimal
36 support for atomic operations may be missing, making OVS very
37 slow (see lib/ovs-atomic.h).
39 - libssl, from OpenSSL, is optional but recommended if you plan to
40 connect the Open vSwitch to an OpenFlow controller. libssl is
41 required to establish confidentiality and authenticity in the
42 connections from an Open vSwitch to an OpenFlow controller. If
43 libssl is installed, then Open vSwitch will automatically build
46 - libcap-ng, written by Steve Grubb, is optional but recommended. It
47 is required to run OVS daemons as a non-root user with dropped root
48 privileges. If libcap-ng is installed, then Open vSwitch will
49 automatically build with support for it.
51 - Python 2.7. You must also have the Python six library.
53 On Linux, you may choose to compile the kernel module that comes with
54 the Open vSwitch distribution or to use the kernel module built into
55 the Linux kernel (version 3.3 or later). See the [FAQ.md] question
56 "What features are not available in the Open vSwitch kernel datapath that
57 ships as part of the upstream Linux kernel?" for more information on
58 this trade-off. You may also use the userspace-only implementation,
59 at some cost in features and performance (see [INSTALL.userspace.md]
60 for details). To compile the kernel module on Linux, you must also
61 install the following:
63 - A supported Linux kernel version. Please refer to [README.md] for a
64 list of supported versions.
66 For optional support of ingress policing, you must enable kernel
67 configuration options NET_CLS_BASIC, NET_SCH_INGRESS, and
68 NET_ACT_POLICE, either built-in or as modules. (NET_CLS_POLICE is
69 obsolete and not needed.)
71 On kernels before 3.11, the ip_gre module, for GRE tunnels over IP
72 (NET_IPGRE), must not be loaded or compiled in.
74 To configure HTB or HFSC quality of service with Open vSwitch,
75 you must enable the respective configuration options.
77 To use Open vSwitch support for TAP devices, you must enable
80 - To build a kernel module, you need the same version of GCC that
81 was used to build that kernel.
83 - A kernel build directory corresponding to the Linux kernel image
84 the module is to run on. Under Debian and Ubuntu, for example,
85 each linux-image package containing a kernel binary has a
86 corresponding linux-headers package with the required build
89 If you are working from a Git tree or snapshot (instead of from a
90 distribution tarball), or if you modify the Open vSwitch build system
91 or the database schema, you will also need the following software:
93 - Autoconf version 2.63 or later.
95 - Automake version 1.10 or later.
97 - libtool version 2.4 or later. (Older versions might work too.)
99 To run the unit tests, you also need:
101 - Perl. Version 5.10.1 is known to work. Earlier versions should
104 The datapath tests for userspace and Linux datapaths also rely upon:
106 - pyftpdlib. Version 1.2.0 is known to work. Earlier versions should
109 - GNU wget. Version 1.16 is known to work. Earlier versions should
112 The ovs-vswitchd.conf.db(5) manpage will include an E-R diagram, in
113 formats other than plain text, only if you have the following:
115 - "dot" from graphviz (http://www.graphviz.org/).
117 - Perl. Version 5.10.1 is known to work. Earlier versions should
120 If you are going to extensively modify Open vSwitch, please consider
121 installing the following to obtain better warnings:
123 - "sparse" version 0.4.4 or later
124 (http://www.kernel.org/pub/software/devel/sparse/dist/).
128 - clang, version 3.4 or later
130 - flake8 (for Python code)
132 Also, you may find the ovs-dev script found in utilities/ovs-dev.py useful.
134 Installation Requirements
135 -------------------------
137 The machine on which Open vSwitch is to be installed must have the
140 - libc compatible with the libc used for build.
142 - libssl compatible with the libssl used for build, if OpenSSL was
145 - On Linux, the same kernel version configured as part of the build.
147 - For optional support of ingress policing on Linux, the "tc" program
148 from iproute2 (part of all major distributions and available at
149 http://www.linux-foundation.org/en/Net:Iproute2).
151 - Python 2.7. You must also have the Python six library.
153 On Linux you should ensure that /dev/urandom exists. To support TAP
154 devices, you must also ensure that /dev/net/tun exists.
156 Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD
157 =================================================================
159 Once you have installed all the prerequisites listed above in the
160 Base Prerequisites section, follow the procedures below to bootstrap,
161 to configure and to build the code.
163 Bootstrapping the Sources
164 -------------------------
166 This step is not needed if you have downloaded a released tarball.
167 If you pulled the sources directly from an Open vSwitch Git tree or
168 got a Git tree snapshot, then run boot.sh in the top source directory
169 to build the "configure" script.
174 Configuring the Sources
175 -----------------------
177 Configure the package by running the configure script. You can
178 usually invoke configure without any arguments. For example:
182 By default all files are installed under /usr/local. Open vSwitch also
183 expects to find its database in /usr/local/etc/openvswitch by default.
184 If you want to install all files into, e.g., /usr and /var instead of
185 /usr/local and /usr/local/var and expect to use /etc/openvswitch as the default
186 database directory, add options as shown here:
188 `% ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc`
190 Note that the Open vSwitch installed with packages like .rpm (e.g. via 'yum
191 install' or 'rpm -ivh') and .deb (e.g. via 'apt-get install' or 'dpkg -i') use
192 the above configure options.
194 By default, static libraries are built and linked against. If you
195 want to use shared libraries instead:
197 `% ./configure --enable-shared`
199 To use a specific C compiler for compiling Open vSwitch user
200 programs, also specify it on the configure command line, like so:
202 `% ./configure CC=gcc-4.2`
204 To use 'clang' compiler:
206 `% ./configure CC=clang`
208 To supply special flags to the C compiler, specify them as CFLAGS on
209 the configure command line. If you want the default CFLAGS, which
210 include "-g" to build debug symbols and "-O2" to enable optimizations,
211 you must include them yourself. For example, to build with the
212 default CFLAGS plus "-mssse3", you might run configure as follows:
214 `% ./configure CFLAGS="-g -O2 -mssse3"`
216 Note that these CFLAGS are not applied when building the Linux
217 kernel module. Custom CFLAGS for the kernel module are supplied
218 using the EXTRA_CFLAGS variable when running make. So, for example:
220 `% make EXTRA_CFLAGS="-Wno-error=date-time"`
222 To build the Linux kernel module, so that you can run the
223 kernel-based switch, pass the location of the kernel build
224 directory on --with-linux. For example, to build for a running
227 `% ./configure --with-linux=/lib/modules/`uname -r`/build`
229 If --with-linux requests building for an unsupported version of
230 Linux, then "configure" will fail with an error message. Please
231 refer to the [FAQ.md] for advice in that case.
233 If you wish to build the kernel module for an architecture other
234 than the architecture of the machine used for the build, you may
235 specify the kernel architecture string using the KARCH variable
236 when invoking the configure script. For example, to build for MIPS
239 `% ./configure --with-linux=/path/to/linux KARCH=mips`
241 If you plan to do much Open vSwitch development, you might want to
242 add --enable-Werror, which adds the -Werror option to the compiler
243 command line, turning warnings into errors. That makes it
244 impossible to miss warnings generated by the build.
246 To build with gcov code coverage support, add --enable-coverage,
249 `% ./configure --enable-coverage`
251 The configure script accepts a number of other options and honors
252 additional environment variables. For a full list, invoke
253 configure with the --help option.
255 You can also run configure from a separate build directory. This
256 is helpful if you want to build Open vSwitch in more than one way
257 from a single source directory, e.g. to try out both GCC and Clang
258 builds, or to build kernel modules for more than one Linux version.
261 `% mkdir _gcc && (cd _gcc && ../configure CC=gcc)`
262 `% mkdir _clang && (cd _clang && ../configure CC=clang)`
264 Under certains loads the ovsdb-server and other components perform
265 better when using the jemalloc memory allocator, instead of the glibc
268 If you wish to link with jemalloc add it to LIBS:
270 `% ./configure LIBS=-ljemalloc`
275 1. Run GNU make in the build directory, e.g.:
279 or if GNU make is installed as "gmake":
283 If you used a separate build directory, run make or gmake from that
289 For improved warnings if you installed "sparse" (see "Prerequisites"),
290 add C=1 to the command line.
292 Some versions of Clang and ccache are not completely compatible.
293 If you see unusual warnings when you use both together, consider
294 disabling ccache for use with Clang.
296 2. Consider running the testsuite. Refer to "Running the Testsuite"
297 below, for instructions.
299 3. Become root by running "su" or another program.
301 4. Run "make install" to install the executables and manpages into the
302 running system, by default under /usr/local.
304 5. If you built kernel modules, you may install and load them, e.g.:
306 `% make modules_install`
307 `% /sbin/modprobe openvswitch`
309 To verify that the modules have been loaded, run "/sbin/lsmod" and
310 check that openvswitch is listed.
312 If the `modprobe` operation fails, look at the last few kernel log
313 messages (e.g. with `dmesg | tail`):
315 - Otherwise, the most likely problem is that Open vSwitch was
316 built for a kernel different from the one into which you are
317 trying to load it. Run `modinfo` on openvswitch.ko and on
318 a module built for the running kernel, e.g.:
321 % /sbin/modinfo openvswitch.ko
322 % /sbin/modinfo /lib/modules/`uname -r`/kernel/net/bridge/bridge.ko
325 Compare the "vermagic" lines output by the two commands. If
326 they differ, then Open vSwitch was built for the wrong kernel.
328 - If you decide to report a bug or ask a question related to
329 module loading, please include the output from the `dmesg` and
330 `modinfo` commands mentioned above.
332 6. Initialize the configuration database using ovsdb-tool, e.g.:
334 `% mkdir -p /usr/local/etc/openvswitch`
335 `% ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema`
340 Before starting ovs-vswitchd itself, you need to start its
341 configuration database, ovsdb-server. Each machine on which Open
342 vSwitch is installed should run its own copy of ovsdb-server.
343 Configure it to use the database you created during installation (as
344 explained above), to listen on a Unix domain socket, to connect to any
345 managers specified in the database itself, and to use the SSL
346 configuration in the database:
349 % ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock \
350 --remote=db:Open_vSwitch,Open_vSwitch,manager_options \
351 --private-key=db:Open_vSwitch,SSL,private_key \
352 --certificate=db:Open_vSwitch,SSL,certificate \
353 --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert \
357 (If you built Open vSwitch without SSL support, then omit
358 --private-key, --certificate, and --bootstrap-ca-cert.)
360 Then initialize the database using ovs-vsctl. This is only
361 necessary the first time after you create the database with
362 ovsdb-tool (but running it at any time is harmless):
364 `% ovs-vsctl --no-wait init`
366 Then start the main Open vSwitch daemon, telling it to connect to the
367 same Unix domain socket:
369 `% ovs-vswitchd --pidfile --detach`
371 Now you may use ovs-vsctl to set up bridges and other Open vSwitch
372 features. For example, to create a bridge named br0 and add ports
373 eth0 and vif1.0 to it:
375 `% ovs-vsctl add-br br0`
376 `% ovs-vsctl add-port br0 eth0`
377 `% ovs-vsctl add-port br0 vif1.0`
379 Please refer to ovs-vsctl(8) for more details.
384 When you upgrade Open vSwitch from one version to another, you should
385 also upgrade the database schema:
387 1. Stop the Open vSwitch daemons, e.g.:
390 % kill `cd /usr/local/var/run/openvswitch && cat ovsdb-server.pid ovs-vswitchd.pid`
393 2. Install the new Open vSwitch release by using the same configure options as
394 was used for installing the previous version. If you do not use the same
395 configure options, you can end up with two different versions of Open vSwitch
396 executables installed in different locations.
398 3. Upgrade the database, in one of the following two ways:
400 - If there is no important data in your database, then you may
401 delete the database file and recreate it with ovsdb-tool,
402 following the instructions under "Building and Installing Open
403 vSwitch for Linux, FreeBSD or NetBSD".
405 - If you want to preserve the contents of your database, back it
406 up first, then use "ovsdb-tool convert" to upgrade it, e.g.:
408 `% ovsdb-tool convert /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema`
410 4. Start the Open vSwitch daemons as described under "Building and
411 Installing Open vSwitch for Linux, FreeBSD or NetBSD" above.
415 Upgrading Open vSwitch from one version to the next version with minimum
416 disruption of traffic going through the system that is using that Open vSwitch
417 needs some considerations:
419 1. If the upgrade only involves upgrading the userspace utilities and daemons
420 of Open vSwitch, make sure that the new userspace version is compatible with
421 the previously loaded kernel module.
423 2. An upgrade of userspace daemons means that they have to be restarted.
424 Restarting the daemons means that the OpenFlow flows in the ovs-vswitchd daemon
425 will be lost. One way to restore the flows is to let the controller
426 re-populate it. Another way is to save the previous flows using a utility
427 like ovs-ofctl and then re-add them after the restart. Restoring the old flows
428 is accurate only if the new Open vSwitch interfaces retain the old 'ofport'
431 3. When the new userspace daemons get restarted, they automatically flush
432 the old flows setup in the kernel. This can be expensive if there are hundreds
433 of new flows that are entering the kernel but userspace daemons are busy
434 setting up new userspace flows from either the controller or an utility like
435 ovs-ofctl. Open vSwitch database provides an option to solve this problem
436 through the other_config:flow-restore-wait column of the Open_vSwitch table.
437 Refer to the ovs-vswitchd.conf.db(5) manpage for details.
439 4. If the upgrade also involves upgrading the kernel module, the old kernel
440 module needs to be unloaded and the new kernel module should be loaded. This
441 means that the kernel network devices belonging to Open vSwitch is recreated
442 and the kernel flows are lost. The downtime of the traffic can be reduced
443 if the userspace daemons are restarted immediately and the userspace flows
444 are restored as soon as possible.
446 The ovs-ctl utility's "restart" function only restarts the userspace daemons,
447 makes sure that the 'ofport' values remain consistent across restarts, restores
448 userspace flows using the ovs-ofctl utility and also uses the
449 other_config:flow-restore-wait column to keep the traffic downtime to the
450 minimum. The ovs-ctl utility's "force-reload-kmod" function does all of the
451 above, but also replaces the old kernel module with the new one. Open vSwitch
452 startup scripts for Debian, XenServer and RHEL use ovs-ctl's functions and it
453 is recommended that these functions be used for other software platforms too.
458 This section describe Open vSwitch's built-in support for various test
459 suites. You must bootstrap, configure and build Open vSwitch (steps are
460 in "Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD"
461 above) before you run the tests described here. You do not need to
462 install Open vSwitch or to build or load the kernel module to run
463 these test suites. You do not need supervisor privilege to run these
469 Open vSwitch includes a suite of self-tests. Before you submit patches
470 upstream, we advise that you run the tests and ensure that they pass.
471 If you add new features to Open vSwitch, then adding tests for those
472 features will ensure your features don't break as developers modify
473 other areas of Open vSwitch.
475 Refer to "Testsuites" above for prerequisites.
477 To run all the unit tests in Open vSwitch, one at a time:
479 This takes under 5 minutes on a modern desktop system.
481 To run all the unit tests in Open vSwitch, up to 8 in parallel:
482 `make check TESTSUITEFLAGS=-j8`
483 This takes under a minute on a modern 4-core desktop system.
485 To see a list of all the available tests, run:
486 `make check TESTSUITEFLAGS=--list`
488 To run only a subset of tests, e.g. test 123 and tests 477 through 484:
489 `make check TESTSUITEFLAGS='123 477-484'`
490 (Tests do not have inter-dependencies, so you may run any subset.)
492 To run tests matching a keyword, e.g. "ovsdb":
493 `make check TESTSUITEFLAGS='-k ovsdb'`
495 To see a complete list of test options:
496 `make check TESTSUITEFLAGS=--help`
498 The results of a testing run are reported in tests/testsuite.log.
499 Please report test failures as bugs and include the testsuite.log in
502 If the build was configured with "--enable-coverage" and the "lcov"
503 utility is installed, you can run the testsuite and generate a code
504 coverage report by using "make check-lcov". All of the options for
505 TESTSUITEFLAGS are available, so you can e.g.:
506 `make check-lcov TESTSUITEFLAGS=-j8 -k ovn`
508 If you have "valgrind" installed, then you can also run the testsuite
509 under valgrind by using "make check-valgrind" in place of "make
510 check". All the same options are available via TESTSUITEFLAGS. When
511 you do this, the "valgrind" results for test `<N>` are reported in files
512 named `tests/testsuite.dir/<N>/valgrind.*`. You may find that the
513 valgrind results are easier to interpret if you put "-q" in
514 ~/.valgrindrc, since that reduces the amount of output.
516 Sometimes a few tests may fail on some runs but not others. This is
517 usually a bug in the testsuite, not a bug in Open vSwitch itself. If
518 you find that a test fails intermittently, please report it, since the
519 developers may not have noticed. You can make the testsuite
520 automatically rerun tests that fail, by adding RECHECK=yes to the
521 "make" command line, e.g.:
522 `make check TESTSUITEFLAGS=-j8 RECHECK=yes`
527 OFTest is an OpenFlow protocol testing suite. Open vSwitch includes a
528 Makefile target to run OFTest with Open vSwitch in "dummy mode". In
529 this mode of testing, no packets travel across physical or virtual
530 networks. Instead, Unix domain sockets stand in as simulated
531 networks. This simulation is imperfect, but it is much easier to set
532 up, does not require extra physical or virtual hardware, and does not
533 require supervisor privileges.
535 To run OFTest with Open vSwitch, first read and follow the
536 instructions under "Testsuites" above. Second, obtain a copy of
537 OFTest and install its prerequisites. You need a copy of OFTest that
538 includes commit 406614846c5 (make ovs-dummy platform work again).
539 This commit was merged into the OFTest repository on Feb 1, 2013, so
540 any copy of OFTest more recent than that should work. Testing OVS in
541 dummy mode does not require root privilege, so you may ignore that
544 Optionally, add the top-level OFTest directory (containing the "oft"
545 program) to your $PATH. This slightly simplifies running OFTest later.
547 To run OFTest in dummy mode, run the following command from your Open
548 vSwitch build directory:
549 `make check-oftest OFT=<oft-binary>`
550 where `<oft-binary>` is the absolute path to the "oft" program in
553 If you added "oft" to your $PATH, you may omit the OFT variable
556 By default, "check-oftest" passes "oft" just enough options to enable
557 dummy mode. You can use OFTFLAGS to pass additional options. For
558 example, to run just the basic.Echo test instead of all tests (the
559 default) and enable verbose logging:
560 `make check-oftest OFT=<oft-binary> OFTFLAGS='--verbose -T basic.Echo'`
562 If you use OFTest that does not include commit 4d1f3eb2c792 (oft:
563 change default port to 6653), merged into the OFTest repository in
564 October 2013, then you need to add an option to use the IETF-assigned
566 `make check-oftest OFT=<oft-binary> OFTFLAGS='--port=6653'`
568 Please interpret OFTest results cautiously. Open vSwitch can fail a
569 given test in OFTest for many reasons, including bugs in Open vSwitch,
570 bugs in OFTest, bugs in the "dummy mode" integration, and differing
571 interpretations of the OpenFlow standard and other standards.
573 Open vSwitch has not been validated against OFTest. Please do report
574 test failures that you believe to represent bugs in Open vSwitch.
575 Include the precise versions of Open vSwitch and OFTest in your bug
576 report, plus any other information needed to reproduce the problem.
581 Ryu is an OpenFlow controller written in Python that includes an
582 extensive OpenFlow testsuite. Open vSwitch includes a Makefile target
583 to run Ryu in "dummy mode". See "OFTest" above for an explanation of
586 To run Ryu tests with Open vSwitch, first read and follow the
587 instructions under "Testsuites" above. Second, obtain a copy of Ryu,
588 install its prerequisites, and build it. You do not need to install
589 Ryu (some of the tests do not get installed, so it does not help).
591 To run Ryu tests, run the following command from your Open vSwitch
593 `make check-ryu RYUDIR=<ryu-source-dir>`
594 where `<ryu-source-dir>` is the absolute path to the root of the Ryu
595 source distribution. The default `<ryu-source-dir>` is `$srcdir/../ryu`
596 where $srcdir is your Open vSwitch source directory, so if this
597 default is correct then you make simply run `make check-ryu`.
599 Open vSwitch has not been validated against Ryu. Please do report
600 test failures that you believe to represent bugs in Open vSwitch.
601 Include the precise versions of Open vSwitch and Ryu in your bug
602 report, plus any other information needed to reproduce the problem.
607 Open vSwitch also includes a suite of tests specifically for datapath
608 functionality, which can be run against the userspace or kernel datapaths.
609 If you are developing datapath features, it is recommended that you use
610 these tests and build upon them to verify your implementation.
612 The datapath tests make some assumptions about the environment. They
613 must be run under root privileges on a Linux system with support for
614 network namespaces. For ease of use, the OVS source tree includes a
615 vagrant box to invoke these tests. Running the tests inside Vagrant
616 provides kernel isolation, protecting your development host from kernel
617 panics or configuration conflicts in the testsuite. If you wish to run
618 the tests without using the vagrant box, there are further instructions
623 *Requires Vagrant (version 1.7.0 or later) and a compatible hypervisor*
625 You must bootstrap and configure the sources (steps are in "Building
626 and Installing Open vSwitch for Linux, FreeBSD or NetBSD" above) before
627 you run the steps described here.
629 A Vagrantfile is provided allowing to compile and provision the source
630 tree as found locally in a virtual machine using the following command:
634 This will bring up a Fedora 23 VM by default. If you wish to use a
635 different box or a vagrant backend not supported by the default box,
636 the `Vagrantfile` can be modified to use a different box as base.
638 The VM can be reprovisioned at any time:
642 OVS out-of-tree compilation environment can be set up with:
645 vagrant provision --provision-with configure_ovs,build_ovs
647 This will set up an out-of-tree build environment inside the VM in
648 /root/build. The source code can be found in /vagrant.
650 To recompile and reinstall OVS in the VM using RPM:
653 vagrant provision --provision-with configure_ovs,install_rpm
655 Two provisioners are included to run system tests with the OVS kernel
656 module or with a userspace datapath. This tests are different from
657 the self-tests mentioned above. To run them:
660 vagrant provision --provision-with configure_ovs,test_ovs_kmod,test_ovs_system_userspace
662 The results of the testsuite reside in the VM root user's home directory:
671 The datapath testsuite as invoked by Vagrant above may also be run
672 manually on a Linux system with root privileges. These tests may take
673 several minutes to complete, and cannot be run in parallel.
675 #### Userspace datapath
677 To invoke the datapath testsuite with the userspace datapath:
679 make check-system-userspace
681 The results of the testsuite are in tests/system-userspace-traffic.dir/.
685 Make targets are also provided for testing the Linux kernel module.
686 Note that these tests operate by inserting modules into the running
687 Linux kernel, so if the tests are able to trigger a bug in the OVS
688 kernel module or in the upstream kernel then the kernel may panic.
690 To run the testsuite against the kernel module which is currently
691 installed on your system:
695 To install the kernel module from the current build directory and
696 run the testsuite against that kernel module:
700 The results of the testsuite are in tests/system-kmod-traffic.dir/.
702 Continuous Integration with Travis-CI
703 -------------------------------------
705 A .travis.yml file is provided to automatically build Open vSwitch with
706 various build configurations and run the testsuite using travis-ci.
707 Builds will be performed with gcc, sparse and clang with the -Werror
708 compiler flag included, therefore the build will fail if a new warning
711 The CI build is triggered via git push (regardless of the specific
712 branch) or pull request against any Open vSwitch GitHub repository that
713 is linked to travis-ci.
715 Instructions to setup travis-ci for your GitHub repository:
717 1. Go to http://travis-ci.org/ and sign in using your GitHub ID.
718 2. Go to the "Repositories" tab and enable the ovs repository. You
719 may disable builds for pushes or pull requests.
720 3. In order to avoid forks sending build failures to the upstream
721 mailing list, the notification email recipient is encrypted. If you
722 want to receive email notification for build failures, replace the
723 the encrypted string:
724 3.1) Install the travis-ci CLI (Requires ruby >=2.0):
726 3.2) In your Open vSwitch repository:
727 travis encrypt mylist@mydomain.org
728 3.3) Add/replace the notifications section in .travis.yml and fill
729 in the secure string as returned by travis encrypt:
736 (You may remove/omit the notifications section to fall back to
737 default notification behaviour which is to send an email directly
738 to the author and committer of the failing commit. Note that the
739 email is only sent if the author/committer have commit rights for
740 the particular GitHub repository).
742 4. Pushing a commit to the repository which breaks the build or the
743 testsuite will now trigger a email sent to mylist@mydomain.org
748 Please report problems to bugs@openvswitch.org.
750 [README.md]:README.md
751 [INSTALL.Debian.md]:INSTALL.Debian.md
752 [INSTALL.Fedora.md]:INSTALL.Fedora.md
753 [INSTALL.RHEL.md]:INSTALL.RHEL.md
754 [INSTALL.XenServer.md]:INSTALL.XenServer.md
755 [INSTALL.NetBSD.md]:INSTALL.NetBSD.md
756 [INSTALL.DPDK.md]:INSTALL.DPDK.md
757 [INSTALL.userspace.md]:INSTALL.userspace.md