Open Stack

Russell-
Thanks for the references, really good stuff. I'm not sure what the right answer is at this point, but I feel like it's definitely far from a solved problem and at the same time something very important to enterprise adoption.



Tyler Britten
Global Cloud Solutions | EMC2
717.448.4057 | tyler.britten at emc.com | @VMTyler


-----Original Message-----
From: Russell Bryant [mailto:rbryant at redhat.com] 
Sent: Wednesday, December 03, 2014 13:52
To: Britten, Tyler; Jason Venner; Daniel P. Berrange
Cc: Enterprise-wg at lists.openstack.org; Stefano Maffulli
Subject: Re: [Win The Enterprise-wg] libvirtWatchdog status

On 12/03/2014 01:37 PM, Britten, Tyler wrote:
> It seems like the main ask from the 'pets' side of the enterprise is 
> not instance monitoring/recovery, but hypervisor monitoring for 
> instance
> recovery- KVM host fails, something is checking for a heartbeat, and 
> once that host is marked as offline, it would check the db for the 
> instances running on that host and schedule them to start on other 
> remaining hosts. Ovbiously this would require shared ephemeral storage
> (NFS) or limit recovery to boot from volume instances.
> 
> Am I offbase?

Nope, and there have been lots of discussions about how to best accomplish that.  Some think it should be built into Nova.  Others suggest other parts of OpenStack (existing or new components) it should be handled by.  Others (including me) suggest this should be (and can already be) handled by tools outside of OpenStack software.

Some references:

Latest thread from openstack-dev about this:


http://lists.openstack.org/pipermail/openstack-dev/2014-October/048338.html

A blog post of mine about how I think it could be done from outside of OpenStack today:


http://blog.russellbryant.net/2014/10/15/openstack-instance-ha-proposal/

Unfortunately I haven't been able to follow that up with next steps of prototyping and testing to prove it out in more detail.

--
Russell Bryant