On 10/06/2015 04:34 PM, Matthew Booth wrote:
> Hi, Roman,
>
> Evacuated has been on my radar for a while and this post has prodded me
> to take a look at the code. I think it's worth starting by explaining
> the problems in the current solution. Nova client is currently
> responsible for doing thi
Hi Matthew,
Thanks for bringing some light on what problems has nova with evacuation of an
instance. It is very important to have those limitations in mind when preparing
final solution. Or to fix them, as you proposed.
Nevertheless, I would say that evacuationD does more than what calling 'nov
Hi, Roman,
Evacuated has been on my radar for a while and this post has prodded me to
take a look at the code. I think it's worth starting by explaining the
problems in the current solution. Nova client is currently responsible for
doing this evacuate. It does:
1. List all instances on the source
- Original Message -
> From: "Roman Dobosz"
> To: "OpenStack Development Mailing List"
>
> Hi all,
>
> The case of automatic evacuation (or resurrection currently), is a topic
> which surfaces once in a while, but it isn't yet fully supported by
> OpenStack and/or by the cluster service
Roman,
Here are some things that may help you:
In Mistral we’ve been aware of this post-message-processing ACK problem since
we began to use oslo.messaging and we’ve been communicating with oslo team in
order to fix that. Patch [1] is supposed to help us finally solve it. I would
encourage you
Hi all,
The case of automatic evacuation (or resurrection currently), is a topic
which surfaces once in a while, but it isn't yet fully supported by
OpenStack and/or by the cluster services. There was some attempts to
bring the feature into OpenStack, however it turns out it cannot be
easily i
