On 23 May 2015 at 04:43, Assaf Muller <[email protected]> wrote: > There's no real reason as far as I'm aware, just an implementation > decision. >
This is inaccurate. There is a reason(s), and this has been asked before: http://lists.openstack.org/pipermail/openstack/2014-March/005950.html http://lists.openstack.org/pipermail/openstack/2014-April/006865.html In a nutshell, the design decision that led to the existing architecture is due to the way OVS handles packets and interact with netfilter. The fact that we keep asking the same question clearly shows lack of documentation, both developer and user facing. I'll get this fixed once and for all. Thanks, Armando > > > > On 21 במאי 2015, at 01:48, Na Zhu <[email protected]> wrote: > > Dear, > > > When OVS plugin is used with GRE option in Neutron, I see that each > compute > node has br-tun and br-int bridges created. > > I'm trying to understand why we need the additional br-tun bridge here. > Can't we create tunneling ports in br-int bridge, and have br-int relay > traffic between VM ports and tunneling ports directly? Why do we have to > introduce another br-tun bridge? > > > Regards, > Juno Zhu > Staff Software Engineer, System Networking > China Systems and Technology Lab (CSTL), IBM Wuxi > Email: [email protected] > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
