Comment 13 for bug 1445089

@brad I don't think that disabling the ARP proxy feature is "defeating the purpose of having L2Population". L2population does two things :
-1/ Partial-mesh : it creates vxlan tunnels dynamically and efficiently, without having to create full-meshed tunnels between every nodes. For instances, if l2pop is not turned on with the ovs agent, vxlan tunnels will exist on each nodes, even if nodes are not hosting any VM in that vxlan network segment.
-2/ ARP responder : it populates arp tables to avoid flooding of arp requests in the network fabric.

So removing the "proxy" mode for vxlan interfaces will only disable the second feature of l2pop.

I think a reasonable patch would be to add a config parameter to disable the proxy mode for the linux bridge agent. This config parameter already exists for the ovs agent, since ovs didn't have the ARP responder feature by the time l2pop has been implemented. It is called "arp_responder" in the [agent] section of the config file of the ovs agent. It might be a good idea to reuse the same parameter name in this context.

Then, having this config parameter set to "false" or "true" by default depends on which feature we want to prioritize.

I would go for having it set to "false" by default, since being able to implement HA scenario with a VIP when l2pop is in use seems more important than getting rid of ARP broadcasting messages in the network fabric.