Thanks Armando. Another question: Every compute node that hosts instances with floating IPs has an IP from the external network pool. If the SNAT is done by the Network Node what is the reason for the compute node to have an external IP? BR, Itzik On 02/11/2015 08:13 PM, Armando M. wrote: > L2pop is a requirement. > > With the existing agent-based architecture, L2pop is used to update > the FDB tables on the compute hosts to make east/west traffic possible > whenever a new port is created or existing one is updated. > > Cheers, > Armando > > On 10 February 2015 at 23:07, Itzik Brown <itzikb at redhat.com > <mailto:itzikb at redhat.com>> wrote: > > Hi, > > In the Networking guide [1] there is a requirement for l2 > population both as > a mechanism driver and in OVS agent when enabling DVR. > Is this is a requirement and if so what is the reason? > > Thanks, > Itzik > > > [1] http://docs.openstack.org/networking-guide/content/ha-dvr.html > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150211/5ed7467a/attachment.html>