Hi Noel, On 22 October 2014 01:57, Noel Burton-Krahn n...@pistoncloud.com wrote: Hi Armando, Sort of... but what happens when the second one dies? You mean, you lost both (all) agents? In this case, yes you'd need to resurrect the agents or move the networks to another available agent.
Thanks for the pointer! I like how the first google hit for this is: Add details on dhcp_agents_per_network option for DHCP agent HA https://bugs.launchpad.net/openstack-manuals/+bug/1370934 :) Seems reasonable to set dhcp_agents_per_network 1. What happens when a DHCP agent dies? Does the
No, unfortunately when the DHCP agent dies there isn't automatic rescheduling at the moment. On Mon, Oct 20, 2014 at 11:56 PM, Noel Burton-Krahn n...@pistoncloud.com wrote: Thanks for the pointer! I like how the first google hit for this is: Add details on dhcp_agents_per_network option for
We currently have a mechanism for restarting the DHCP agent on another node, but we'd like the new agent to take over all the old networks of the failed dhcp instance. Right now, since dhcp agents are distinguished by host, and the host has to match the host of the ovs agent, and the ovs agent's
As far as I can tell when you specify: dhcp_agents_per_network = X 1 The server binds the network to all the agents (up to X), which means that you have multiple instances of dnsmasq serving dhcp requests at the same time. If one agent dies, there is no fail-over needed per se, as the other
Hi Armando, Sort of... but what happens when the second one dies? If one DHCP agent dies, I need to be able to start a new DHCP agent on another host and take over from it. As far as I can tell right now, when one DHCP agent dies, another doesn't take up the slack. I have the same problem wit
See dhcp_agents_per_network in neutron.conf. https://bugs.launchpad.net/neutron/+bug/1174132 2014-10-21 6:47 GMT+08:00 Noel Burton-Krahn n...@pistoncloud.com: I've been working on failover for dhcp and L3 agents. I see that in , multiple dhcp agents can host the same network. However, it