Comment 0 for bug 1819730

Currently if I deploy Neutron with L3HA the vrrp traffic (keepalived) will always go over the network provided by the first provider defined in tenant_network_types (which in most cases will be gre). If a deployment is not using the same physical interface/bond for the tenant and external traffic then it does not make sense to have things setup like this since if there is a problem with the external network access to a host, keepalived will not notice unless the same problem impacts the tenant network. Therefore we should allow users to configure the l3_ha_network_type and l3_ha_network_physical_name config options to allow a separate provider to be used of one is available.