We are moving off vmware due to licensing costs and we don’t use vsphere at all 
for what we pay for it. So we are looking to go to KVM and using openvswitch 
like vmare vswitch. I’m wondering if there is anything special that needs to be 
done other then set a vlan tag on a fake bridge interface. I want to have my 
layout like  

kvm host subnet: 10.10.7.0/24

Then the vlans are like

vlan 2 = 10.10.2.0/24
        3 = 10.10.3.0/24
        etc..

So on my kvm host I want to have the vlan ports for the lans but not have an ip 
on that space attached to the host. Also have guests on those vlans that are 
able to talk to other hosts and other guests on other vlans.

I’m not looking to do any layer 3 routing on the openvswitch or anything.. Just 
pass everything back to the firewall to do the rules there.

Right now I have something like

root@ubuntu:~# ifconfig
br0       Link encap:Ethernet  HWaddr 00:0c:29:bd:22:04
          inet addr:10.10.7.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:febd:2204/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:515827 errors:0 dropped:0 overruns:0 frame:0
          TX packets:95870 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:661622023 (661.6 MB)  TX bytes:111551273 (111.5 MB)

br0.2     Link encap:Ethernet  HWaddr be:29:ca:d9:77:ec
          inet6 addr: fe80::bc29:caff:fed9:77ec/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:9188 (9.1 KB)

br0.3     Link encap:Ethernet  HWaddr 42:d5:1e:03:21:2d
          inet6 addr: fe80::40d5:1eff:fe03:212d/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:828 (828.0 B)

eth0      Link encap:Ethernet  HWaddr 00:0c:29:bd:22:04
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:614253 errors:0 dropped:0 overruns:0 frame:0
          TX packets:137263 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:678858706 (678.8 MB)  TX bytes:173171595 (173.1 MB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:37389 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37389 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:107136820 (107.1 MB)  TX bytes:107136820 (107.1 MB)

macvtap0  Link encap:Ethernet  HWaddr 52:54:00:15:66:ea
          inet6 addr: fe80::5054:ff:fe15:66ea/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B)  TX bytes:8360 (8.3 KB)


root@ubuntu:~# ovs-vsctl show
fd5477bf-dcaf-4581-b3fa-6b23a90a6506
    Bridge "br0"
        Port "br0"
            trunks: [2, 3, 4, 5, 6, 7, 8]
            Interface "br0"
                type: internal
        Port "br0.2"
            tag: 2
            Interface "br0.2"
                type: internal
        Port "br0.3"
            tag: 3
            Interface "br0.3"
                type: internal
        Port "eth0"
            Interface "eth0"
    ovs_version: “2.0.1"




Is that enough and i just tell kvm to use the right br device in bridge mode?


Thanks!


Mike Zupan


Senior Linux Engineer | Recurly



m...@recurly.com


P 917-645-2315

recurly.com (http://recurly.com/)

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to