make openvswitch compatible with oVirt (tight with brctl)

It has also been integrated into many virtual management systems including OpenStack, openQRM, OpenNebula and oVirt. 

Network ovirtmgmt is not attached to any interface on host 150.

[root@150 openvswitch-1.9.3]# brctl show
bridge name     bridge id               STP enabled     interfaces
ovirtmgmt               /sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
0000.00221960778f       no

[root@150 openvswitch-1.9.3]# cat INSTALL.bridge 
              Replacing a Linux Bridge with Open vSwitch
              ==========================================

This file documents how Open vSwitch may be used as a drop-in
replacement for a Linux kernel bridge in an environment that includes
elements that are tightly tied to the Linux bridge tools
(e.g. "brctl") and architecture.  We recommend directly using the
management tools provided with Open vSwitch rather than these
compatibility hooks for environments that are not tightly tied to the
Linux bridging tools; they are more efficient and better reflect the
actual operation and status.

Installation Procedure
----------------------

The procedure below explains how to use the Open vSwitch bridge
compatibility support.  This procedure is written from the perspective
of a system administrator manually loading and starting Open vSwitch
in bridge compatibility mode, but of course in practice one would want
to update system scripts to follow these steps.  If you do edit your
system configuration files to start Open vSwitch at boot time, make
sure that it starts up before any bridge configuration (e.g. before
any calls to "brctl" or "ifup" of any bridge interfaces), to ensure
that the Open vSwitch kernel modules are loaded before the Linux
kernel bridge module.

1. Build, install, and start up the Open vSwitch kernel modules and
   userspace programs as described in INSTALL.

   It is important to run "make install", because some Open vSwitch
   programs expect to find files in locations selected at installation
   time.  The instructions below assume that files are installed in
   their default locations, under /usr/local.

2. Load the brcompat kernel module (which was built in step 1), e.g.:

      % insmod datapath/linux/brcompat.ko

   (openvswitch.ko should already have been loaded.)

3. Start ovs-brcompatd:

      % ovs-brcompatd --pidfile --detach

   (ovsdb-server and ovs-vswitchd should already have been loaded.)

4. Now you should be able to manage the Open vSwitch using brctl and
   related tools.  For example, you can create an Open vSwitch bridge,
   add interfaces to it, then print information about bridges with the
   commands:

      % brctl addbr br0
      % brctl addif br0 eth0
      % brctl addif br0 eth1
      % brctl show

   Each of these commands actually uses or modifies the Open vSwitch
   configuration database, then notifies the ovs-vswitchd daemon of
   the change.  For example, after executing the commands above
   starting from an empty configuration file, "ovs-vsctl list-ports
   br0" should show that bridge br0 contains two ports, eth0 and eth1.

[root@150 openvswitch-1.9.3]# locate brcompat.ko
/lib/modules/2.6.32-431.20.3.el6.x86_64/extra/openvswitch/brcompat.ko
[root@150 openvswitch-1.9.3]# lsmod|grep brcom
[root@150 openvswitch-1.9.3]# insmod /lib/modules/2.6.32-431.20.3.el6.x86_64/extra/openvswitch/brcompat.ko
[root@150 openvswitch-1.9.3]# lsmod|grep brcom
brcompat                5905  0 
openvswitch            96678  1 brcompat

[root@150 openvswitch-1.9.3]# ovs-brcompatd --pidfile --detach
2014-08-06T00:23:14Z|00001|brcompatd|WARN|Bridge compatibility is deprecated and may be removed no earlier than February 2013
[root@150 openvswitch-1.9.3]# ps -ewf|grep ovs-b
root     18676     1  0 08:23 ?        00:00:00 ovs-brcompatd --pidfile --detach

[root@150 openvswitch-1.9.3]# brctl show
bridge name     bridge id               STP enabled     interfaces
;vdsmdummy;             8000.000000000000       no
ovirtmgmt               /sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
0000.00221960778f       no

[root@150 openvswitch-1.9.3]# ovs-vsctl show
fb8f1987-c908-4a8f-bc2c-1f8c19f034fc
    Bridge ovirtmgmt
        Port ovirtmgmt
            Interface ovirtmgmt
                type: internal
        Port "em1"
            Interface "em1"
    ovs_version: "1.9.3"

[root@150 openvswitch-1.9.3]# brctl addbr br1
[root@150 openvswitch-1.9.3]# brctl show
bridge name     bridge id               STP enabled     interfaces
;vdsmdummy;             8000.000000000000       no
br1             /sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
/sys/class/net/br1/bridge: No such file or directory
0000.a28e5dc5ae47       no
ovirtmgmt               /sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
/sys/class/net/ovirtmgmt/bridge: No such file or directory
0000.00221960778f       no