Neutron cores,
I have submitted the change [1] which is related to the thread [2]
in January.
Unfortunately it did not attract the interest of many core reviewers,
and only time has passed.
Now it is pointed that it may need FFE/SSE, and the opinion of the
core is a bit divided about implement
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
On Jan 6, 2015, at 8:05 AM, Carl Baldwin wrote:
> 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
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
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 t
