Open Stack

On Thu, Jan 8, 2015 at 8:49 AM, McCann, Jack <jack.mccann at hp.com> wrote:

> +1 on need for this feature
>
> The way I've thought about this is we need a mode that stops the
> *automatic*
> scheduling of routers/dhcp-servers to specific hosts/agents, while allowing
> manual assignment of routers/dhcp-servers to those hosts/agents, and where
> any existing routers/dhcp-servers on those hosts continue to operate as
> normal.
>
> The maintenance use case was mentioned: I want to evacuate
> routers/dhcp-servers
> from a host before taking it down, and having the scheduler add new
> routers/dhcp
> while I'm evacuating the node is a) an annoyance, and b) causes a service
> blip
> when I have to right away move that new router/dhcp to another host.
>
> The other use case is adding a new host/agent into an existing environment.
> I want to be able to bring the new host/agent up and into the neutron
> config, but
> I don't want any of my customers' routers/dhcp-servers scheduled there
> until I've
> had a chance to assign some test routers/dhcp-servers and make sure the
> new server
> is properly configured and fully operational.
>
> These are all solid reasons for adding this, and it makes sense to me as
well. From a deployers perspective, these would be a big win.

Given we have already filed a bug, hopefully we can get this addressed soon.

Thanks,
Kyle


> - Jack
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150108/9741acae/attachment.html>