[StarCluster] Re deleting root volumes after termination

[Steve Heistand]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

you can set the device to be deleted on termination with an ec2 command:

ec2-modify-instance-attribute -b "/dev/sda1=:true" 'instance_id'

and then use the starcluster ebsimage command to create a new AMI that
is permanently marked this way. (detaching any nonroot volumes before imaging)

or use the AWS dashboard/cli command to create a new AMI from the running instance.
in that operation there is an option to mark the root volume to be deleted.

If you dont want to create a new AMI then I would suggest something like
the ec2-modify-instance-attribute above placed in a userdata script that
is run at cluster start time.

s


On 09/05/2013 07:09 PM, Lyn Gerner wrote:
> Thanks Rayson, good stuff.
> 
> Do you (does anyone) happen to know a cmd-line way of resetting this on the AMI so
> the instances that boot it always have their vols/devices set to delete on term?  (As
> opposed to having to set this on every volume on every instance that gets launched.)
> I've been scouring the forums and 'net, and haven't come up w/anything slick.
> 
> Thanks, Lyn
> 
> 
> On Wed, Sep 4, 2013 at 6:58 AM, <starcluster-request at mit.edu> wrote:
> 
>> Send StarCluster mailing list submissions to starcluster at mit.edu
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit 
>> http://mailman.mit.edu/mailman/listinfo/starcluster or, via email, send a message
>> with subject or body 'help' to starcluster-request at mit.edu
>> 
>> You can reach the person managing the list at starcluster-owner at mit.edu
>> 
>> When replying, please edit your Subject line so it is more specific than "Re:
>> Contents of StarCluster digest..."
>> 
>> Today's Topics:
>> 
>> 1. Re: root volumes after termination (Rayson Ho) 2. Re: Loadbalancing error
>> against ubuntu QIIME AMI (Rayson Ho) 3. Re: root volumes after termination (Steve
>> Heistand)
>> 
>> 
>> ---------- Forwarded message ---------- From: Rayson Ho <raysonlogin at gmail.com> To:
>> Steve Heistand <steve.heistand at nasa.gov> Cc: "starcluster at mit.edu"
>> <starcluster at mit.edu> Date: Wed, 4 Sep 2013 12:12:52 -0400 Subject: Re:
>> [StarCluster] root volumes after termination OK, start a 1-node EBS StarCluster
>> (t1.micro is good) and make sure to use your AMI instead of the standard
>> StarCluster AMI. Then go to the AWS management Console, select the instance of the
>> 1-node cluster, and click the "Root Device:" (eg. Root Device: sda1) link, and you
>> will see information about the root device like:
>> 
>> Root device type: ebs Attachment time: 2012-12-12 Block device status: attached 
>> Delete on termination: Yes
>> 
>> Rayson
>> 
>> ================================================== Open Grid Scheduler - The
>> Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ 
>> http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html
>> 
>> 
>> 
> 
> 
> 
> _______________________________________________ StarCluster mailing list 
> StarCluster at mit.edu http://mailman.mit.edu/mailman/listinfo/starcluster
> 

- -- 
************************************************************************
 Steve Heistand                          NASA Ames Research Center
 email: steve.heistand at nasa.gov          Steve Heistand/Mail Stop 258-6
 ph: (650) 604-4369                      Bldg. 258, Rm. 232-5
 Scientific & HPC Application            P.O. Box 1
 Development/Optimization                Moffett Field, CA 94035-0001
************************************************************************
 "Any opinions expressed are those of our alien overlords, not my own."

# For Remedy                        #
#Action: Resolve                    #	
#Resolution: Resolved               #
#Reason: No Further Action Required #
#Tier1:	User Code                   #
#Tier2:	Other                       #
#Tier3:	Assistance                  #
#Notification: None                 #
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAlIp6+4ACgkQoBCTJSAkVrE5bQCcDZLlvFBj2f3YhfVfdCfHltjL
VIUAoNLNHqpqN4sSrQrRtaDCb/tTapPi
=u1Z5
-----END PGP SIGNATURE-----