<div dir="ltr">I was working on <a href="https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance">https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance</a>. Hadn't looked at it because of FF, will restore the patch soon.<br>

</div><div class="gmail_extra"><br clear="all"><div>Thanks<br>Mahesh<br>Developer | ThoughtWorks | +1 (210) 716 1767</div>

<br><br><div class="gmail_quote">On Tue, Oct 8, 2013 at 5:20 PM, Alex Glikson <span dir="ltr"><<a href="mailto:GLIKSON@il.ibm.com" target="_blank">GLIKSON@il.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<font face="Times New Roman" size="3">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 (<a href="https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance" target="_blank"><font color="blue" face="Times New Roman" size="3">https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance</a><font face="Times New Roman" size="3">).

Then, it would make sense to have the logic that evacuates an entire host

(<a href="https://blueprints.launchpad.net/python-novaclient/+spec/find-and-evacuate-host" target="_blank"><font color="blue" face="Times New Roman" size="3">https://blueprints.launchpad.net/python-novaclient/+spec/find-and-evacuate-host</a><font face="Times New Roman" size="3">).

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 face="Times New Roman" size="3">Regards,</font>

<br><font face="Times New Roman" size="3">Alex</font>

<br>

<br>

<br>

<br>

<br><font color="#5f5f5f" face="sans-serif" size="1">From:      

 </font><font face="sans-serif" size="1">Syed Armani <<a href="mailto:dce3062@gmail.com" target="_blank">dce3062@gmail.com</a>></font>

<br><font color="#5f5f5f" face="sans-serif" size="1">To:      

 </font><font face="sans-serif" size="1">OpenStack Development

Mailing List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>>, </font>

<br><font color="#5f5f5f" face="sans-serif" size="1">Date:      

 </font><font face="sans-serif" size="1">09/10/2013 12:04 AM</font>

<br><font color="#5f5f5f" face="sans-serif" size="1">Subject:    

   </font><font face="sans-serif" size="1">Re: [openstack-dev]

[nova] automatically evacuate instances on compute failure</font>

<br>

<hr noshade><div class="HOEnZb"><div class="h5">

<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 color="blue" size="3"><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 color="blue" size="3"><u><br>

</u></font><a href="https://blueprints.launchpad.net/nova/+spec/evacuate-instance-automatically" target="_blank"><font color="blue" size="3"><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 color="blue" size="3"><u><br>

</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><font color="blue" size="3"><u>OpenStack-dev@lists.openstack.org</u></font></a><font color="blue" size="3"><u><br>

</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font color="blue" size="3"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a>

<br><tt><font>_______________________________________________<br>

OpenStack-dev mailing list<br>

<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>

</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font><br>

</font></tt>

<br></div></div><br>_______________________________________________<br>

OpenStack-dev mailing list<br>

<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>

<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>

<br></blockquote></div><br></div>