HI,
To make clear I'd like note:
1. openvswich is available in distros, both in
Ubuntu 13.04 and Fedora 18
2. brcompat is removed in openvswitch v1.10.0
Please have a look at http://openvswitch.org/releases/NEWS-1.10.0
So IMHO, we should not recommend brcompat.
3. some tutorial on Ubuntu below:
-------------------------------------
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
DISTRIB_CODENAME=raring
DISTRIB_DESCRIPTION="Ubuntu 13.04"
# apt-cache search openvswitch-switch
openvswitch-common - Open vSwitch common components
openvswitch-switch - Open vSwitch switch implementations
openvswitch-brcompat - Open vSwitch bridge compatibility support
openvswitch-datapath-dkms - Open vSwitch datapath module source - DKMS
version
openvswitch-datapath-source - Open vSwitch datapath module source -
module-assistant version
# apt-get install openvswitch-switch
## NOTE: I setup openvswitch without brcompat
# dpkg -l | grep openvswitch
ii openvswitch-common 1.9.0-0ubuntu1
amd64 Open vSwitch common components
ii openvswitch-switch 1.9.0-0ubuntu1
amd64 Open vSwitch switch implementations
## NOTE: bridge and openvswitch kernel modules coexist
# lsmod | egrep "(openvswitch|bridge)"
bridge 99533 0
stp 12976 1 bridge
llc 14552 2 stp,bridge
openvswitch 43117 0
## NOTE: Of cource, we can't create the same name bridge in both
## because they are netdevs.
# brctl addbr br0
# ovs-vsctl add-br br0
## NOTE: cli returned 0, but the operation was failed at last.
# echo $?
0
# ovs-dpctl show
## NOTE: show nothing
# tail /var/log/openvswitch/ovs-vswitchd.log
2013-05-29T23:56:54Z|00007|dpif|WARN|datapath br0 already exists but
cannot be opened: No such device
2013-05-29T23:56:54Z|00008|ofproto_dpif|ERR|failed to open datapath br0:
No such device
2013-05-29T23:56:54Z|00009|ofproto|ERR|failed to open datapath br0: No
such device
2013-05-29T23:56:54Z|00010|bridge|ERR|failed to create bridge br0: No
such device
## NOTE: So we revert it
# ovs-vsctl del-br br0
## NOTE: and create with another name
# ovs-vsctl add-br cloudbr0
## NOTE: now the datapath cloudbr0 shows up
# ovs-dpctl show
system@cloudbr0:
lookups: hit:0 missed:0 lost:0
flows: 0
port 0: cloudbr0 (internal)
## NOTE: Now the system shows like this:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000000000000 no
virbr0 8000.000000000000 yes
# ovs-vsctl show
cae16abf-bbd6-4837-9b56-77f7dd8415b4
Bridge "cloudbr0"
Port "cloudbr0"
Interface "cloudbr0"
type: internal
ovs_version: "1.9.0"
-------------------------------------
