[openstack-dev] [Neutron][L3] Stop agent scheduling without topping sevices
blak111 at gmail.com
Fri Jan 9 00:47:35 UTC 2015
Is there another openstack service that allows this so we can make the API
consistent between the two when this change is made?
On Thu, Jan 8, 2015 at 3:09 PM, Carl Baldwin <carl at ecbaldwin.net> wrote:
> I added a link to @Jack's post to the ML to the bug report . I am
> willing to support @Itsuro with reviews of the implementation and am
> willing to consult if you need and would like to ping me.
>  https://bugs.launchpad.net/neutron/+bug/1408488
> On Thu, Jan 8, 2015 at 7: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
> > scheduling of routers/dhcp-servers to specific hosts/agents, while
> > manual assignment of routers/dhcp-servers to those hosts/agents, and
> > any existing routers/dhcp-servers on those hosts continue to operate as
> > The maintenance use case was mentioned: I want to evacuate
> > from a host before taking it down, and having the scheduler add new
> > 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
> > 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.
> > - Jack
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev