Open Stack

On Wed, Apr 24, 2013 at 10:02:10AM -0400, Russell Bryant wrote:
> On 04/24/2013 09:51 AM, Leen Besselink wrote:
> > On Wed, Apr 24, 2013 at 09:35:19AM -0400, Russell Bryant wrote:
> >> On 04/23/2013 08:20 PM, Robert Collins wrote:
> >>> +1 on using Heat to orchestrate the response to a node failure.
> >>
> >> Yeah, it's quite clever, I like it.  It's as if you TripleO folks are on
> >> to something here.  ;-)
> >>
> > 
> > I thought the same thing, until I realized that maybe not everyone wants to setup
> > OpenStack on OpenStack. But might still want VM HA.
> 
> If folks want to diverge from "the OpenStack way", that's perfectly
> fine.  In that case we just need to make sure all of the primitives are
> there for someone to implement their own solution.
> 

If Heat will be the OpenStack way, then I'll have some time in a couple of hours
to rewrite the etherpad blueprint to make that the main way of handling it.

> As far as I know, the compute API already exposes the primitives
> necessary here.  If you detect a compute node failure using your Thing,
> you can use live-migrate or evacuate, depending on whether the compute
> node is on its way to dying, or is already dead.
> 
> -- 
> Russell Bryant
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev