Hi, You can see in the review [1] that doude first proposed an ebtables manager to implement the ARP responder for ovs. OVS 2.1 is now able to manage an ARP responder based on flow [2], so he switches his implementation to a flow based ARP responder (please, have a look at patches history). ebtables driver seems more interesting since this implementation would be compatible with any ovs version, but VM needs to be plugged to a linux bridge and with ovsfirewalldriver [3], nova won't need to plug VM to a linux bridge anymore, so ARP responder based on ebtables won't work.
[1]https://review.openstack.org/#/c/49227/ [2]https://review.openstack.org/#/c/49227/27/neutron/plugins/ml2/drivers/l2pop/README [3]https://blueprints.launchpad.net/neutron/+spec/ovs-firewall-driver On Thu, Feb 13, 2014 at 9:51 AM, Édouard Thuleau <thul...@gmail.com> wrote: > Hi, > > On Havana, a local ARP responder is available if you use the ML2 with the > l2-pop MD and the Linux Bridge (natively implemented by the Linux kernel > VXLAN module). > It's not (yet [1]) available with the OVS agent. The proposed OVS > implementation use new OVS flows integrated on branch 2.1. > > Just few remarks about the ML2 MD l2-pop. Two important bugs persists: > - One [2] impacts all the MD l2-pop (Linux Bridge and OVS agents). Merged on > trunk and waiting to be backported [3] > - Another one [4] impacts only the OVS agent stills waiting review. > > [1] https://review.openstack.org/#/c/49227/ > [2] https://review.openstack.org/#/c/63913/ > [3] https://review.openstack.org/#/c/71821/ > [4] https://review.openstack.org/#/c/63917/ > > Édouard. > > > On Thu, Feb 13, 2014 at 4:57 AM, Nick Ma <skywalker.n...@gmail.com> wrote: >> >> Hi all, >> >> I'm running a OpenStack Havana cloud on pre-production stage using >> Neutron ML2 VxLAN. I'd like to incorporate l2-population to get rid of >> tunnel broadcast. >> >> However, it seems that ARP Proxy has NOT been implemented yet for Open >> vSwitch for Havana and also the latest master branch. >> >> I find that ebtables arpreply can do it and then put some corresponding >> flow rules into OVS. >> >> Could anyone provide more hints on how to implement it in l2-pop? >> >> thanks, >> >> -- >> >> Nick Ma >> skywalker.n...@gmail.com >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
