I was working on https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance. Hadn't looked at it because of FF, will restore the patch soon.
Thanks Mahesh Developer | ThoughtWorks | +1 (210) 716 1767 On Tue, Oct 8, 2013 at 5:20 PM, Alex Glikson <glik...@il.ibm.com> wrote: > 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 (* > https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance > *<https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance>). > Then, it would make sense to have the logic that evacuates an entire host ( > * > https://blueprints.launchpad.net/python-novaclient/+spec/find-and-evacuate-host > *<https://blueprints.launchpad.net/python-novaclient/+spec/find-and-evacuate-host>). > 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). > > Regards, > Alex > > > > > From: Syed Armani <dce3...@gmail.com> > To: OpenStack Development Mailing List < > openstack-dev@lists.openstack.org>, > Date: 09/10/2013 12:04 AM > Subject: Re: [openstack-dev] [nova] automatically evacuate > instances on compute failure > ------------------------------ > > > > Hi Folks, > > 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. > > Thanks. > > Cheers, > Syed Armani > > > On Wed, Sep 25, 2013 at 11:46 PM, Chris Friesen <* > chris.frie...@windriver.com* <chris.frie...@windriver.com>> wrote: > 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: > * > ** > https://blueprints.launchpad.net/nova/+spec/evacuate-instance-automatically > *<https://blueprints.launchpad.net/nova/+spec/evacuate-instance-automatically> > > However, the comments there seem to indicate that the code that > orchestrates the evacuation shouldn't go into nova (referencing the Havana > design summit). > > 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? > > Thanks, > Chris > > _______________________________________________ > OpenStack-dev mailing list* > **OpenStack-dev@lists.openstack.org* <OpenStack-dev@lists.openstack.org>* > **http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev*<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
