Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Instance type ignored during launch of imagehost #388

johnbot1 opened this Issue · 0 comments

1 participant


When building an imagehost with a defined instance type on the command line the image type is ignored and instead reverts to the default cluster template's master instance type. To confirm, changing the default templates master image in the config type also changes the imagehosts instance type even though it's explicitly defined in the command.

Not a huge deal but I think it conflicts with the documentation and may cause some confusion.

starcluster -c ~/.starcluster/config.special start -o -s 1 -b 0.70 -i m3.2xlarge -n ami-0e48233e imagehost

>>> Using default cluster template: small
>>> Validating cluster template settings...
>>> Cluster template settings are valid
>>> Starting cluster...
>>> Launching a 1-node cluster...
>>> Launching master node (ami: ami-0e48233e, type: m3.medium)...
>>> Creating security group @sc-imagehost...
>>> Waiting for instances to propagate...
1/1 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 100%  
>>> Starting cluster took 0.041 mins
@jtriley jtriley closed this issue from a commit
@jtriley docs: update image host command with -I,-m options
Using these options instead of -i and -n prevents an issue where the
default cluster template in the config may override these values if
master_instance_type and master_image_id are defined. This ensures the
user gets exactly the instance type and base AMI they are expecting when
launching the image host regardless of their config.

closes gh-388
@jtriley jtriley closed this in 3d5c75a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.