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 <o...@valinux.co.jp>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
