Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Add support for R3 instance types #393

Merged
merged 1 commit into from Apr 22, 2014

Conversation

Projects
None yet
2 participants
Contributor

corydolphin commented Apr 15, 2014

This addresses #392

I added classification as HIMEM_TYPES, as they are not cluster compute instances, and are set to replace the M2 types.

They are also HVM only types, which makes them somewhat special.

Let me know if this classification is inaccurate or there are any other changes required. I would love to see this merged so I can stop using a private build :-)

@corydolphin corydolphin referenced this pull request Apr 15, 2014

Closed

Add R3 instance types #392

Owner

jtriley commented Apr 15, 2014

@wcdolphin Thanks for the PR. Indeed we need to double check the classification. Fortunately I've built a tool in $STARCLUSTER_REPO/utils/missingcloud.py that figures this out automatically by launching spot requests to see if EC2 accepts the configuration and then immediately cancelling them so that no instances are launched (and hence no costs). To use this tool:

$ cd $STARCLUSTER_REPO/utils
$ starcluster shell
[~]> import missingcloud
[~]> mc = missingcloud.MissingCloud()
[~]> mc.fetch()
[~]> print mc.INSTANCE_TYPES
[~]> print mc.REGION_TYPES_MAP
[~]> print mc.PLACEMENT_GROUP_TYPES
[~]> print mc.PLACEMENT_GROUP_REGIONS
[~]> print mc.HVM_ONLY_TYPES
[~]> print mc.HVM_TYPES

NOTE: Even though the tool cancels the spot requests immediately after creating them (if it was able to of course) please be aware that this tool could in theory launch instances and cost money.

Anyway we will need to update your PR if it doesn't match the missingcloud.py tool. I will double check with this tool before I merge regardless.

Contributor

corydolphin commented Apr 15, 2014

After running missingcloud.py, it seems that the format of instance-types has changed.

On the instance-types page, previous generations are not shown, and the system architecture is no longer shown.

Contributor

corydolphin commented Apr 21, 2014

@jtriley is there any chance you have had a chance to check this out? For my user case, R3 instances are less than half the price of previous instances.

With respect to classification, I am confident that these instances are 64bit HVM AMI only.

R3 instances have high-memory (up to 244 GiB of RAM), and require 64-bit operating systems to take advantage of that capacity. HVM AMIs provide superior performance in comparison to paravirtual (PV) AMIs on high-memory instance types. For these reasons, R3 instances support 64-bit HVM AMIs only. In addition, HVM AMIs are required to leverage the benefits of enhanced networking.

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/r3-instances.html

@jtriley jtriley merged commit 397d285 into jtriley:develop Apr 22, 2014

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details

jtriley added a commit that referenced this pull request Apr 22, 2014

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