[Openstack] Why is Neutron OVS topology the way it is?

Michael Dorman mdorman at godaddy.com
Tue Mar 11 14:22:30 UTC 2014


I believe this is so that security groups can be applied using iptables on those qbrXXX interfaces.  At least that's how it works in our implementation under Havana.


From: Dan Nanni <xmodulo at gmail.com<mailto:xmodulo at gmail.com>>
Date: Tuesday, March 11, 2014 8:06 AM
To: "openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>" <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>
Subject: [Openstack] Why is Neutron OVS topology the way it is?

Hi,

I was playing with OpenStack Neutron with OVS plugin. When I launch VMs, I noticed that there is a Linux bridge (qbrxxx) created for each VM, which is then connected to the OVS bridge (ovs-int). See the following.

        VM0           VM2
           |                 |
      qbrXXX        qbrYYY  (per-VM linux bridges)
           |                 |
           |                 |
        br-int (OVS bridge)
                    |
                 br-eth

My question is, why couldn't VMs be directly connected to br-int (without qbr Linux bridges)? Why do we create additional Linux bridges between OVS bridge and VMs? What is the role of Linux bridges here?

Thanks!
-Dan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140311/4b0a8ce5/attachment.html>


More information about the Openstack mailing list