<font size=3 face="Times New Roman">Seems that this can be broken into
3 incremental pieces. First, would be great if the ability to schedule
a single 'evacuate' would be finally merged (</font><a href="https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance"><font size=3 color=blue face="Times New Roman"><u>https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance</u></font></a><font size=3 face="Times New Roman">).
Then, it would make sense to have the logic that evacuates an entire host
(</font><a href="https://blueprints.launchpad.net/python-novaclient/+spec/find-and-evacuate-host"><font size=3 color=blue face="Times New Roman"><u>https://blueprints.launchpad.net/python-novaclient/+spec/find-and-evacuate-host</u></font></a><font size=3 face="Times New Roman">).
The reasoning behind suggesting that this should not necessarily be in
Nova is, perhaps, that it *can* be implemented outside Nova using the indvidual
'evacuate' API. Finally, it should be possible to close the loop and invoke
the evacuation automatically as a result of a failure detection (not clear
how exactly this would work, though). Hopefully we will have at least the
first part merged soon (not sure if anyone is actively working on a rebase).</font>
<br>
<br><font size=3 face="Times New Roman">Regards,</font>
<br><font size=3 face="Times New Roman">Alex</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Syed Armani <dce3062@gmail.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">OpenStack Development
Mailing List <openstack-dev@lists.openstack.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">09/10/2013 12:04 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
[nova] automatically evacuate instances on compute failure</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Hi Folks,</font>
<br>
<br><font size=3>I am also very much curious about this. Earlier this bp
had a dependency on query scheduler, which is now merged. It will be very
helpful if anyone can throw some light on the fate of this bp.</font>
<br>
<br><font size=3>Thanks.</font>
<br>
<br><font size=3>Cheers,</font>
<br><font size=3>Syed Armani</font>
<br><font size=3><br>
</font>
<br><font size=3>On Wed, Sep 25, 2013 at 11:46 PM, Chris Friesen <</font><a href=mailto:chris.friesen@windriver.com target=_blank><font size=3 color=blue><u>chris.friesen@windriver.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=3>I'm interested in automatically evacuating instances in
the case of a failed compute node. I found the following blueprint
that covers exactly this case:<br>
</font><font size=3 color=blue><u><br>
</u></font><a href="https://blueprints.launchpad.net/nova/+spec/evacuate-instance-automatically" target=_blank><font size=3 color=blue><u>https://blueprints.launchpad.net/nova/+spec/evacuate-instance-automatically</u></font></a><font size=3><br>
<br>
However, the comments there seem to indicate that the code that orchestrates
the evacuation shouldn't go into nova (referencing the Havana design summit).<br>
<br>
Why wouldn't this type of behaviour belong in nova? (Is there a summary
of discussions at the summit?) Is there a recommended place where
this sort of thing should go?<br>
<br>
Thanks,<br>
Chris<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target=_blank><font size=3 color=blue><u>OpenStack-dev@lists.openstack.org</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target=_blank><font size=3 color=blue><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a>
<br><tt><font size=2>_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>