Open Stack

+2 

I understand the desire to have these kinds of 'features' but we also need
to be constantly asking ourselves, is this really the right long-term
solution and IMHO it isn't. Use your cloud like a utility instead of a
'sacred' set of machines/vms/... that must never go down and I think the
experience will be much more pleasant in the long term.

-Josh

-----Original Message-----
From: Jay Pipes <jaypipes at gmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at lists.openstack.org>
Date: Monday, April 14, 2014 at 11:05 AM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] deliver the vm-level HA to improve the
business continuity with openstack

>On Mon, 2014-04-14 at 10:56 -0700, Steven Dake wrote:
>> On 04/14/2014 10:46 AM, Tim Bell wrote:
>> > Can Heat control/monitor a VM which it has not created and restart it
>>(potentially on a different hypervisor with live migration) ?
>> >
>> > Tim
>> Tim,
>> 
>> No it sure can't.
>
>But a 10-20 line shell script could, calling nova CLI commands.
>
>I think the point here is that we see pushes like this to treat VMs as
>pets and we've so far been able to successfully push back on these
>(anti)feature requests, pointing out that this kind of thing generally
>is antithetical to a utility cloud model and antithetical to the
>horizontal scale-out architecture that cloud espouses (i.e. don't have a
>single point of failure that requires this kind of setup).
>
>/me waits for someone to use the word "enterprise".
>
>-jay
>
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev