Carl, Thank you for your comment.
It seems there is no clear opinion about whether bug report or buleprint is better. So I submitted a bug report for the moment so that the requirememt is not forgotten. https://bugs.launchpad.net/neutron/+bug/1408488 Thanks. Itsuro Oda On Tue, 6 Jan 2015 09:05:19 -0700 Carl Baldwin <[email protected]> wrote: > Itsuro, > > 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. > > Carl > > On Mon, Jan 5, 2015 at 4:13 PM, Itsuro ODA <[email protected]> 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 <[email protected]> > > > > > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA <[email protected]> _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
