It would be desirable to be able to be hide an agent from scheduling
but no one has stepped up to make this happen.  Come to think of it,
I'm not sure that a bug or blueprint has been filed yet to address it
though it is something that I've wanted for a little while now.


On Mon, Jan 5, 2015 at 4:13 PM, Itsuro ODA <> wrote:
> Neutron experts,
> I want to stop scheduling to a specific {dhcp|l3}_agent without
> stopping router/dhcp services on it.
> I expected setting admin_state_up of the agent to False is met
> this demand. But this operation stops all services on the agent
> in actuality. (Is this behavior intended ? It seems there is no
> document for agent API.)
> I think admin_state_up of agents should affect only scheduling.
> If it is accepted I will submit a bug report and make a fix.
> Or should I propose a blueprint for adding function to stop
> agent's scheduling without stopping services on it ?
> I'd like to hear neutron experts' suggestions.
> Thanks.
> Itsuro Oda
> --
> Itsuro ODA <>
> _______________________________________________
> OpenStack-dev mailing list

OpenStack-dev mailing list

Reply via email to