a -- yes!
MASTER_INSTANCE_TYPE = c1.medium
MASTER_IMAGE_ID = ami-XXXXXX
NODE_IMAGE_ID = ami-XXXXXX
NODE_INSTANCE_TYPE = cr1.8xlarge
b -- in config do:
In the [cluster NAME] section:
PLUGINS = sge
Then define your sge plugin with:
setup_class = starcluster.plugins.sge.SGEPlugin
master_is_exec_host = False
You can also force the master to be a spot instance by using 'starcluster start --force-spot-master', which can save serious cash (90%).
On Jan 29, 2013, at 9:02 AM, "Sergio Mafra" <sergiohmafra_at_gmail.com<mailto:sergiohmafra_at_gmail.com>> wrote:
If we are supposed to have the instances running for a long time, LoadBlancer can help us a lot, turning on and off when is needed.
I wonder if we can make this more smarter and cheaper, launching the master node as a m1.small instance, taking care only for communication and queue managemente, leaving the heavier job for the compute nodes, that can take advantage of cluster type instance and placement groups.
So my question is:
a) Can we have a cluster with differente instance types - Master and Compute nodes?
b) How to exclude Master node from being a computacional node in the job queue?
All the best,
StarCluster mailing list
Received on Tue Jan 29 2013 - 09:31:25 EST