Enterprise! We drive the ³VM=Cattle² message pretty hard. Part of onboarding a property to our cloud, and allowing them to serve traffic from VMs is explaining the transient nature of VMs. I broadcast the message that all compute resources die, and if your day/week/month is ruined because of a single compute instance going away, then you¹re doing something Very Wrong. :)
-James :)= On 4/14/14, 11:05 AM, "Jay Pipes" <jaypi...@gmail.com> wrote: >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@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