On Sun, Oct 4, 2015 at 6:19 PM, Kyle Mestery <mest...@mestery.com> wrote: > On Sun, Oct 4, 2015 at 5:20 PM, Ansis Atteka <aatt...@nicira.com> wrote: >> >> Mention: >> 1. that these instructions have been tested with CentOS 7 (which is >> almost identical distribution to RHEL 7). >> 2. directory where rpm packages that were just built can be found. >> 3. mention SElinux implications that could prevent OVS from starting, >> if not using designated OVS directories. >> >> Signed-off-by: Ansis Atteka <aatt...@nicira.com> >> --- >> INSTALL.RHEL.md | 11 ++++++++++- >> 1 file changed, 10 insertions(+), 1 deletion(-) >> >> diff --git a/INSTALL.RHEL.md b/INSTALL.RHEL.md >> index 8746bc6..9aefc09 100644 >> --- a/INSTALL.RHEL.md >> +++ b/INSTALL.RHEL.md >> @@ -5,7 +5,7 @@ This document describes how to build and install Open >> vSwitch on a Red >> Hat Enterprise Linux (RHEL) host. If you want to install Open vSwitch >> on a generic Linux host, see [INSTALL.md] instead. >> >> -We have tested these instructions with RHEL 5.6 and RHEL 6.0. >> +We have tested these instructions with RHEL 5.6 and RHEL 6.0 and CentOS >> 7. >> > Similar comment here, are the RHEL 5.6 and 6.0 builds still being tested > automatically somehow?
Since Red Hat still supports RHEL 5.6 I would argue that latest OVS should also claim to support it. I have to admit that I haven't tried these instructions on RHEL 5.6 recently. > >> Building Open vSwitch for RHEL >> ------------------------------ >> @@ -105,6 +105,7 @@ $HOME/rpmbuild/SOURCES. >> directory. Then unpack the tarball and "cd" into its root, e.g.: >> >> ``` >> + cd $HOME/rpmbuild/SOURCES >> tar xzf openvswitch-x.y.z.tar.gz >> cd openvswitch-x.y.z >> ``` >> @@ -139,6 +140,8 @@ $HOME/rpmbuild/SOURCES. >> rhel/openvswitch-kmod-rhel6.spec >> ``` >> >> +10. Find the created packages in $HOME/rpmbuild/RPMS directory >> + >> This produces an "kmod-openvswitch" RPM for each kernel variant, in >> this example: "kmod-openvswitch", "kmod-openvswitch-debug", and >> "kmod-openvswitch-kdump". >> @@ -149,6 +152,12 @@ Geneve, GRE, VXLAN, LISP etc., they will either have >> to manually add iptables >> firewall rules to allow the tunnel traffic or add it through a startup >> script >> (Please refer to the "enable-protocol" command in the ovs-ctl(8) >> manpage). >> >> +RHEL based distributions nowadays ship with SElinux enabled in enforcing >> mode >> +by default. This means that, if you have problems starting Open vSwitch, >> then >> +first check that Open vSwitch is configured to run inside its SElinux >> confined >> +area. For more details see "man (8) openvswitch_selinux" that is >> distributed >> +with selinux-policy-devel package on your distribution. >> + >> Red Hat Network Scripts Integration >> ----------------------------------- >> >> -- >> 2.1.4 >> >> _______________________________________________ >> dev mailing list >> dev@openvswitch.org >> http://openvswitch.org/mailman/listinfo/dev > > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
