Hi Kevin,
The current method outlined in [1] is to manually assign networks to dhcp
agents. I need to be able to kill the node running the dhcp agent and
start it up on another node without manual intervention. Someone else
pointed me to the dhcp_agents_per_network option which I'm looking into
The current suggested way for DHCP agent fault tolerance is multiple agents
per network. Is there a reason you don't want to use that option?
On Oct 20, 2014 5:13 PM, "Noel Burton-Krahn" wrote:
> Thanks, Robert.
>
> So, ML2 needs the host attribute to match to bind the port. My other
> requireme
Thanks, Robert.
So, ML2 needs the host attribute to match to bind the port. My other
requirement is that the dhcp agent must be able to migrate to a new host on
failover. The issue there is that if the dhcp service starts on a new host
with a new host name, then it will not take over the network
Hi Noel,
The ML2 plugin uses the binding:host_id attribute of port to control
port binding. For compute ports, nova sets binding:host_id when
creating/updating the neutron port, and ML2's openvswitch mechanism
driver will look in agents_db to make sure the openvswitch L2 agent is
running on t
