Wow, I can't believe I never thought of that. Just tested c3.large > c3.8xlarge transformation, and it worked just fine … AWS CLI for the command line win!
starcluster start -i c3.large -c mycluster mycluster
starcluster stop -c mycluster
starcluster lc ## wait till the nodes are all 'stopped'
for ID in $(starcluster lc mycluster 2>/dev/null | grep -e node[0-9][0-9][0-9] -e master | awk '{print $3}'); do
echo $ID
# the magic:
aws ec2 modify-instance-attribute --instance-id $ID --instance-type c3.8xlarge
done
starcluster start -x mycluster
Seems like that could be pretty easily integrated into StarCluster.
-Hugh
From: Rayson Ho [mailto:raysonlogin_at_gmail.com]
Sent: Thursday, September 18, 2014 1:18 AM
To: Ramon Ramirez-Linan
Cc: MacMullan, Hugh; starcluster_at_mit.edu
Subject: Re: [StarCluster] Changing iinstance type for everynode in the cluster
I've never tried something like this myself, but I believe it would work if you stop the EBS cluster (*NOT* terminate), and then change the instance type from the EC2 management Console, and then restart the cluster, then StarCluster would happily reconfig the cluster for you:
http://star.mit.edu/cluster/docs/latest/manual/launch.html#stopping-an-ebs-backed-cluster
Just a reboot won't do it, as the private IP address changes when you change the instance type, and /etc/hosts would need to be changed again.
(Test with a 2-node t1.micro cluster and change the type to t2.micro before doing anything experimental on a real production cluster.)
Rayson
On Wed, Sep 17, 2014 at 10:53 PM, Ramon Ramirez-Linan <rlinan_at_navteca.com<mailto:rlinan_at_navteca.com>> wrote:
Hi,
Is there a way of changing the instance type for the entire cluster after it has already be launched?
I want to launch a 30 nodes cluster with a cheaper instance type to ingest data on each node's volume. Each node has a 1TB EBS attached and there is no need to share data between nodes (no nfs or anything). Then once the data is injected on each node I want to be able to change the cluster instances to a more expensive one (more CPU/RAM)
Will cluster reboot let me do that?
Thanks in advance
Received on Thu Sep 18 2014 - 10:22:09 EDT