Tom, <br><br>I dont know if croning the "Terminate" for instances in "shutdown" state is a good idea, after a Physical node restart the instances running in that node stays in shutdown mode after the node comes back, you can "re-awake" them by issuing nova reboot, maybe a cleaner an usefull script will try to "reboot" the instance and if doest succeed terminate them, just an idea.<br>
<br>Regards<br>Lele<br><br><div class="gmail_quote">On Tue, Jul 5, 2011 at 1:50 AM, Tom Fifield <span dir="ltr"><<a href="mailto:fifieldt@unimelb.edu.au">fifieldt@unimelb.edu.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
Echoing this request - it's very handy on Amazon EC2 when a shutdown -h now command results in instance termination.<br>
<br>
Is there a reason for the difference in OpenStack, or is this just how it was implemented? :)<br>
<br>
<br>
I'd probably be writing a cron script to look at the database to 'terminate' instances in 'shutdown' state and thereby freeing their resources...<br>
<br>
<br>
Regards,<br><font color="#888888">
<br>
Tom</font><div><div></div><div class="h5"><br>
<br>
On 07/03/2011 11:44 PM, Terry.Rankine@csiro.au wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Wont it need my EC2 credentials on the VM then?<br>
<br>
The credentials used to start the VM are not stored on the VM. I guess I can pass them in via the start-up string, but I would prefer if there was another way.<br>
<br>
Any other thoughts?<br>
<br>
Terry<br>
______________________________<u></u>__<br>
From: Mike Marrotte [<a href="mailto:marrotte@gmail.com" target="_blank">marrotte@gmail.com</a>]<br>
Sent: Friday, 1 July 2011 7:47 PM<br>
To: Rankine, Terry (CESRE, Kensington)<br>
Cc:<<a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.<u></u>openstack.org</a>><br>
Subject: Re: [Openstack-operators] New to Open Stack - shutdown vs terminate<br>
<br>
Sure. Just install the euca2ools on the guest and write a script.<br>
<br>
Sent from my iPhone<br>
<br>
On Jul 1, 2011, at 1:07 AM,<Terry.Rankine@csiro.au<<u></u>mailto:<a href="mailto:Terry.Rankine@csiro.au" target="_blank">Terry.Rankine@csiro.au</a>><u></u>> wrote:<br>
<br>
Hi Guys<br>
I am building an ‘worker image’ for an on-demand specific ‘compute this’ workflow.<br>
The image is totally aware of its success or failure of the ‘compute this’ task, and uploads its output back to S3 storage.<br>
Since the VM is the best thing to know about success/failure, I figure it should also be the right thing to determine its end of life (shutdown-dont destroy on failure for debugging, and shutdown-terminate-release on success).<br>
I would like it to automatically shutdown (and terminate releasing all resources it held – public IP etc) on success, and I would like the VM itself be able to do this. A ‘shutdown –h now’ put the image into shutdown mode, but not terminated and never released the held resources.<br>
Is it possible for the VM to ‘shutdown and terminate’ itself?<br>
Terry<br>
______________________________<u></u>_________________<br>
Openstack-operators mailing list<br>
<a href="mailto:Openstack-operators@lists.openstack.org" target="_blank">Openstack-operators@lists.<u></u>openstack.org</a><mailto:<a href="mailto:Openstack-operators@lists.openstack.org" target="_blank">Openstack<u></u>-operators@lists.openstack.org</a><u></u>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-operators</a><br>
______________________________<u></u>_________________<br>
Openstack-operators mailing list<br>
<a href="mailto:Openstack-operators@lists.openstack.org" target="_blank">Openstack-operators@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-operators</a><br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
Openstack-operators mailing list<br>
<a href="mailto:Openstack-operators@lists.openstack.org" target="_blank">Openstack-operators@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-operators</a><br>
</div></div></blockquote></div><br>