In a previous post we pointed to instructions and some common tasks for using Star Cluster to create an HPC cluster on the fly in Amazon Web Services. Now we will focus on some options for optimizing your use of Star Cluster.
Cutting the Fat - Your Head Node is to Big
Use Spot For Lower Costs
Almost every Star command that starts an instance can be created as a bid, using the -b <bid price> options.
Switch Regions and/or Availability Zone
|c3.8xlarge us-east-1 24h price history|
Changing regions in Star Cluster:
Update the region name and the region host (the machine that accepts AWS API commands from star) and the availability zone.
#get values from:
$ starcluster listregions
$ starcluster listzones
AWS_REGION_NAME = us-west-2Create a new key pair for each region, so repeat that step with a new name for they key in the Star cluster Quick Start, and update the [key key-name-here] for your cluster config.
AWS_REGION_HOST = ec2.us-west-2.amazonaws.com
AVAILABILITY_ZONE = us-west-2c
The AMI names are also per region so when you switch regions you need to update the name of the image to boot, in general select an HVM image$ starcluster createkey mykey-us-west-2 -o ~/.ssh/mykey-us-west-2.rsa
[key mykey] KEY_LOCATION=~/.ssh/mykey-us-west-2.rsa
#get list of AMI images for region
$ starcluster listpublic
Get a Reserved Instance for your Head/Master Node
Switch to Instance Store
Most users clusters will not resize long enough to have this mater, contact firstname.lastname@example.org if you want to switch. Just remember to terminate your cluster, not just stop it. If you stop it the EBS volumes remain.