X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=INSTALL;h=68805ee1ac65d327c9f4fe796353e4df4e1c0643;hb=db273f62751541557a9e24a46629e26b75348c99;hp=275e86e3a099f95e18322d761ef05eb0727411b5;hpb=6494ea4c962118de72410f62045603279eb967da;p=sliver-openvswitch.git diff --git a/INSTALL b/INSTALL index 275e86e3a..68805ee1a 100644 --- a/INSTALL +++ b/INSTALL @@ -1,9 +1,9 @@ - How to Install Open vSwitch on Linux and FreeBSD - ================================================ + How to Install Open vSwitch on Linux, FreeBSD and NetBSD + ======================================================== This document describes how to build and install Open vSwitch on a -generic Linux or FreeBSD host. For specifics around installation on a -specific platform, please see one of these files: +generic Linux, FreeBSD, or NetBSD host. For specifics around installation +on a specific platform, please see one of these files: - INSTALL.Debian - INSTALL.Fedora @@ -16,13 +16,11 @@ Build Requirements To compile the userspace programs in the Open vSwitch distribution, you will need the following software: - - A make program, e.g. GNU make. BSD make should also work. + - GNU make. - The GNU C compiler. We generally test with version 4.1, 4.2, or 4.3. - - pkg-config. We test with version 0.22. - - libssl, from OpenSSL, is optional but recommended if you plan to connect the Open vSwitch to an OpenFlow controller. libssl is required to establish confidentiality and authenticity in the @@ -145,8 +143,8 @@ software: (On Debian "lenny" the above can be installed with "apt-get install python-json python-qt4 python-zopeinterface python-twisted-conch".) -Building and Installing Open vSwitch for Linux or FreeBSD -========================================================= +Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD +================================================================= Once you have installed all the prerequisites listed above in the Base Prerequisites section, follow the procedure below to build. @@ -192,22 +190,26 @@ Prerequisites section, follow the procedure below to build. additional environment variables. For a full list, invoke configure with the --help option. -3. Run make in the top source directory: +3. Run GNU make in the top source directory, e.g.: % make - On FreeBSD you may need to use GNU make (gmake) or NetBSD make - (bmake) instead of the native make. + or if GNU make is installed as "gmake": + + % gmake For improved warnings if you installed "sparse" (see - "Prerequisites"), add C=1 to the "make" command line. + "Prerequisites"), add C=1 to the command line. + +4. Consider running the testsuite. Refer to "Running the Testsuite" + below, for instructions. -4. Become root by running "su" or another program. +5. Become root by running "su" or another program. -5. Run "make install" to install the executables and manpages into the +6. Run "make install" to install the executables and manpages into the running system, by default under /usr/local. -6. If you built kernel modules, you may load them with "insmod", e.g.: +7. If you built kernel modules, you may load them with "insmod", e.g.: % insmod datapath/linux/openvswitch.ko @@ -267,7 +269,7 @@ Prerequisites section, follow the procedure below to build. % make modules_install -7. Initialize the configuration database using ovsdb-tool, e.g.: +8. Initialize the configuration database using ovsdb-tool, e.g.: % mkdir -p /usr/local/etc/openvswitch % ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema @@ -331,7 +333,7 @@ also upgrade the database schema: - If there is no important data in your database, then you may delete the database file and recreate it with ovsdb-tool, following the instructions under "Building and Installing Open - vSwitch for Linux or FreeBSD". + vSwitch for Linux, FreeBSD or NetBSD". - If you want to preserve the contents of your database, back it up first, then use "ovsdb-tool convert" to upgrade it, e.g.: @@ -339,7 +341,60 @@ also upgrade the database schema: % ovsdb-tool convert /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema 4. Start the Open vSwitch daemons as described under "Building and - Installing Open vSwitch for Linux or FreeBSD" above. + Installing Open vSwitch for Linux, FreeBSD or NetBSD" above. + +Running the Testsuite +===================== + +Open vSwitch includes a testsuite. Before you submit patches +upstream, we advise that you run the tests and ensure that they pass. +If you add new features to Open vSwitch, then adding tests for those +features will ensure your features don't break as developers modify +other areas of Open vSwitch. + +You must configure and build Open vSwitch (steps 1 through 3 in +"Building and Installing Open vSwitch for Linux, FreeBSD or NetBSD" above) +before you run the testsuite. You do not need to install Open vSwitch +or to build or load the kernel module to run the testsuite. You do +not need supervisor privilege to run the testsuite. + +To run all the unit tests in Open vSwitch, one at a time: + make check +This takes under 5 minutes on a modern desktop system. + +To run all the unit tests in Open vSwitch, up to 8 in parallel: + make check TESTSUITEFLAGS=-j8 +This takes under a minute on a modern 4-core desktop system. + +To see a list of all the available tests, run: + make check TESTSUITEFLAGS=--list + +To run only a subset of tests, e.g. test 123 and tests 477 through 484: + make check TESTSUITEFLAGS='123 477-484' +(Tests do not have inter-dependencies, so you may run any subset.) + +To run tests matching a keyword, e.g. "ovsdb": + make check TESTSUITEFLAGS='-k ovsdb' + +To see a complete list of test options: + make check TESTSUITEFLAGS=--help + +The results of a testing run are reported in tests/testsuite.log. +Please report test failures as bugs and include the testsuite.log in +your report. + +If you have "valgrind" installed, then you can also run the testsuite +under valgrind by using "make check-valgrind" in place of "make +check". All the same options are available via TESTSUITEFLAGS. When +you do this, the "valgrind" results for test are reported in files +named tests/testsuite.dir//valgrind.*. You may find that the +valgrind results are easier to interpret if you put "-q" in +~/.valgrindrc, since that reduces the amount of output. + +Sometimes a few tests may fail on some runs but not others. This is +usually a bug in the testsuite, not a bug in Open vSwitch itself. If +you find that a test fails intermittently, please report it, since the +developers may not have noticed. Bug Reporting -------------