Options for VPC Use #366

Closed
craigbruce opened this Issue Feb 10, 2014 · 5 comments

2 participants

@craigbruce

Using 0.95 I generated a new config and edited my cluster stanza to include the required options:

SUBNET_ID=subnet-XXXXXX
PUBLIC_IPS=False

However, when the ec2 instances boot they do get public IPs and the step where starcluster attempts to SSH in fails.

If I use the same file but launch with: starcluster start -N subnet-XXXXXXX --no-public-ips mycluster. It works as expected, no public IPs, ssh access is gained the cluster is configured.

Cheers
Craig

@jtriley
Owner

@craigbruce Fixing this now. Thanks for reporting!

@jtriley jtriley added a commit that closed this issue Feb 12, 2014
@jtriley start: set default value to None for --no-public-ips
By default StarCluster's start command interprets any options that have
a non-None value to be user-specified options. If the default value of
an option is not None then the start command assumes the default value
to be a user specified value and overrides the config with command-line
option values.

In this case the --no-public-ip default value was not None so setting
PUBLIC_IPS in the config had no effect (unless it happened matched the
start command's default for it of course :P) due to the start command
overriding it with the non-None default value.

closes gh-366
bd33131
@jtriley jtriley closed this in bd33131 Feb 12, 2014
@craigbruce

I've just tested this but still have the same results:

>>> Using default cluster template: smallcluster
>>> Validating cluster template settings...
>>> Cluster template settings are valid
>>> Starting cluster...
>>> Launching a 2-node cluster...
>>> Creating security group @sc-vpcdev...
Reservation:r-3bca9d1b

Using the -N options:

>>> Using default cluster template: smallcluster
>>> Validating cluster template settings...
>>> Cluster template settings are valid
>>> Starting cluster...
>>> Launching a 2-node cluster...
>>> Creating security group @sc-vpcdev...
*** WARNING - PUBLIC IPS HAVE BEEN DISABLED!!!

This means StarCluster must be executed from a machine within the cluster's VPC
(vpc-XXXX) otherwise it will hang forever trying to connect to the instances.
Reservation:r-06f6a126
@jtriley
Owner

@craigbruce I think I just found the last remaining culprit. When adding the config setting to static.py I incorrectly set the type to 'str' instead of 'bool'. I'm fixing this now along with another bug and releasing another patch release 0.95.2 today.

@jtriley jtriley reopened this Feb 25, 2014
@jtriley jtriley added a commit that closed this issue Feb 25, 2014
@jtriley static: set public_ip setting type to bool
closes gh-366 (for real)
213ea0d
@jtriley jtriley closed this in 213ea0d Feb 25, 2014
@craigbruce

I can confirm this is fixed in 0.95.2 - thanks!

@jtriley
Owner

@craigbruce Awesome, thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment