Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Nov 22, 2013
  1. @jtriley
  2. @jtriley

    Merge branch 'hotfix-0.94.3' into develop

    jtriley authored
    Conflicts:
    	Changelog
    	README.rst
    	starcluster/awsutils.py
    	starcluster/static.py
  3. @jtriley
  4. @jtriley

    bump version to 0.94.3

    jtriley authored
Commits on Nov 21, 2013
  1. @jtriley
  2. @jtriley

    awsutils: use instance store bmap for 32bit m1.small

    jtriley authored
    For some reason the only way to get StarCluster's custom block device
    mappings for ephemeral drives to work with m1.small and a 32bit EBS AMI
    is to use instance_store=True when calling create_block_device_map.
  3. @jtriley

    use 64bit AMI as default in config template

    jtriley authored
    Update the default config template to use 64bit AMIs given that they run
    everywhere now on all instance types.
  4. @jtriley

    awsutils: omit root snapshot id in custom block dev map

    jtriley authored
    It's unclear whether this never worked or recently stopped working given
    that users at one point in time were able to launch clusters with 0.94.2
    and suddenly can't now. Either way, removing the snapshot id from the
    root device's custom block device mapping when setting
    delete_on_terminate still works and still inherits the AMI's underlying
    root device snapshot anyway.
    
    closes gh-330
Commits on Nov 19, 2013
  1. @jtriley
  2. @jtriley
  3. @jtriley
  4. @jtriley

    node: better fix for gh-304

    jtriley authored
    The previous fix simply blasted all /etc/exports entries for each node
    before exporting paths to nodes. This can potentially kill other export
    paths not being exported by export_fs_to_nodes given that they will not
    be redefined. Added `paths` kwarg to Node.stop_exporting_fs_to_nodes
    that causes only the specified export paths for each node to be removed
    from /etc/exports instead of all entries for each node.
    
    Thanks to @realoptimal for the catch:
    
    jtriley@f7c4967#commitcomment-4640990
  5. @jtriley

    awsutils: use instance store bmap for 32bit m1.small

    jtriley authored
    For some unknown reason the only way to get StarCluster's custom block
    device mappings for ephemeral drives to work with m1.small and a 32bit
    EBS AMI is to use instance_store=True when calling
    create_block_device_map.
    
    closes gh-329
  6. @jtriley
  7. @jtriley

    node: avoid misleading exception in alias property

    jtriley authored
    The Node.alias property was raising an AttributeError in the case that
    userdata is None which is masking the real error that the instance has
    no alias. Fixed this by using a default value of '' when fetching values
    from the user_data dict.
  8. @jtriley

    use 64bit AMI as default in config template

    jtriley authored
    Forgot to update the config template a while ago to default to 64bit
    AMIs given that they run everywhere now on all instance types.
    Discovered this when gh-329 was reported.
Commits on Nov 18, 2013
  1. @jtriley
  2. @jtriley

    Merge branch 'openssh-tty-option' into develop

    jtriley authored
    Conflicts:
    	starcluster/cluster.py
    	starcluster/node.py
    
    closes gh-295
  3. @jtriley

    pep8 clean-up on gh-295

    jtriley authored
Commits on Nov 15, 2013
  1. @jtriley

    config: update VPC comments in config template

    jtriley authored
    Made a note that VPC_ID is optional but if it's specified SUBNET_ID must
    also be provided.
  2. @jtriley

    node: fix for stale NFS entries

    jtriley authored
    closes gh-304
Commits on Nov 14, 2013
  1. @jtriley
  2. @jtriley

    Merge pull request #325 from rayrayson/develop

    jtriley authored
    add support for new c3 instance types
  3. add support for new c3 instance types

    Rayson Ho authored
  4. @jtriley

    Merge branch 'fix-gh-312' into develop

    jtriley authored
    closes gh-291
    closes gh-312
  5. @jtriley

    cluster: always use master's zone if not specified

    jtriley authored
    Updated Cluster._get_cluster_zone to fetch the zone from the master node
    in the case that no availability zone or EBS volumes were specified.
    
    Updated Cluster.zone property to always fetch the cluster zone using
    Cluster._get_cluster_zone.
  6. @jtriley

    node: revert back to using self.alias in is_master()

    jtriley authored
    Another regression from #236
  7. @jtriley
  8. @jtriley

    cluster: consolidate duplicate code in terminate_cluster

    jtriley authored
    The terminate_cluster code added by gh-236 duplicates the work in
    EasyEC2.delete_group. Removed this code in favor of EasyEC2.delete_group
    and added max_retries=60 and retry_delay=5 kwargs to prevent
    EasyEC2.delete_group from looping indefinitely. The default values for
    these new kwargs cause EasyEC2.delete_group to abort after retrying for
    5 minutes.
  9. @jtriley
  10. @jtriley

    addnode: remove dns_prefix kwargs and -P options

    jtriley authored
    ..in favor of storing the dns_prefix in the Cluster's security group
    tags and relying on the Cluster.load_receipt function to restore the
    proper cluster settings used at launch time. This removes the need for
    the -P options to all commands except the start command.
  11. @jtriley

    addnode, removenode: remove -c option

    jtriley authored
    These commands do not and should not support the -c option. This was
    another regression from gh-236.
  12. @jtriley

    terminate: remove --dns-prefix (-P) option

    jtriley authored
    This option isn't needed and was only needed because of gh-236 changing
    how StarCluster loads cluster metadata.
  13. @jtriley

    sshmaster: remove -P option and dns_prefix kwarg

    jtriley authored
    These kwargs/options aren't really necessary and were only needed due to
    gh-236 changing the way StarCluster load's cluster metadata.
  14. @jtriley

    fix regressions from merging gh-236

    jtriley authored
    Turns out gh-236 changed the get_cluster, add_node, and remove_node
    methods in ClusterManager to always fetch the cluster from the config
    which completely circumvents loading the cluster metadata from AWS and
    breaks existing functionality. See gh-193 for reference.
Something went wrong with that request. Please try again.