[StarCluster] starcluster instance types

[Laura Del Caño]

Thanks Eduardo and Hugh,

we might decide to use one of the other existing instance types, but it is
good to know where these are defined in case we need to a different one.

regards
Laura

On Tue, Nov 17, 2015 at 3:59 PM, Eduardo Gurgel Valente <
evalente at navteca.com> wrote:

> Hi Hugh,
>
>   I think the comment and Laura's issue remains.  The latest update didn't
> include all m4 types only m4.10xlarge.  For reference
> https://aws.amazon.com/blogs/aws/the-new-m4-instance-type-bonus-price-reduction-on-m3-c4/
>
> Eduardo
>
> On Tue, Nov 17, 2015 at 9:53 AM, MacMullan, Hugh <
> hughmac at wharton.upenn.edu> wrote:
>
>> To follow up on what Eduardo said, if it's not clear:
>>
>>
>>
>> 1. the 'pip install starcluster' version doesn't contain the latest
>> instance types
>>
>> 2. the repo in GitHub does (updated only 5 days ago)
>>
>>
>>
>> git clone https://github.com/jtriley/StarCluster.git
>>
>> cd StarCluster
>>
>> python setup.py install
>>
>>
>>
>> You should be good to go.
>>
>>
>>
>> Cheers,
>>
>> -Hugh
>>
>>
>>
>> *From:* starcluster-bounces at mit.edu [mailto:starcluster-bounces at mit.edu] *On
>> Behalf Of *Eduardo Gurgel Valente
>> *Sent:* Tuesday, November 17, 2015 9:31 AM
>> *To:* Laura Del Caño <ldelcano at gmail.com>
>> *Cc:* starcluster <starcluster at mit.edu>
>> *Subject:* Re: [StarCluster] starcluster instance types
>>
>>
>>
>> Hi Laura,
>>
>>
>>
>>   While I haven't tried it, it seems that the file starcluster/static.py
>> holds the relevant structures that keep the types.  The full link from
>> github is
>> https://github.com/jtriley/StarCluster/blob/155365d7c9e07e11b5272ddef93e324ecb8c031d/starcluster/static.py
>>
>>   What new types are you looking for?
>>
>>
>>
>> Eduardo
>>
>>
>>
>>
>>
>> On Tue, Nov 17, 2015 at 9:19 AM, Laura Del Caño <ldelcano at gmail.com>
>> wrote:
>>
>> Hi,
>>
>> I am starting to use starcluster to set up our cluster on AWS but I am
>> encountering a problem.
>>
>> According to the config file, instance types must be one of the following:
>>
>> # instance type for all cluster nodes
>> # (options: m3.large, c3.8xlarge, i2.8xlarge, t2.micro, hs1.8xlarge,
>> c1.xlarge, r3.4xlarge, g2.2xlarge, m1.small, c1.medium, m3.2xlarge,
>> c3.2xlarge, m2.xlarge, m2.2xlarge, t2.small, r3.2xlarge, t1.micro,
>> cr1.8xlarge, r3.8xlarge, cc1.4xlarge, m1.medium, r3.large, c3.xlarge,
>> i2.xlarge, m3.medium, cc2.8xlarge, m1.large, cg1.4xlarge, i2.2xlarge,
>> c3.large, i2.4xlarge, c3.4xlarge, r3.xlarge, t2.medium, hi1.4xlarge,
>> m2.4xlarge, m1.xlarge, m3.xlarge)
>>
>> However I can see most of them are AWS previous generation types (not
>> that good and also more expensive).
>>
>> Is this an updated list? Is there a reason for this and/or a way to
>> overcome this limitation?
>>
>> I am on us-east-1 region although I don't know if this depends on regions.
>>
>>
>>
>> thanks alot
>>
>> Laura
>>
>>
>> _______________________________________________
>> StarCluster mailing list
>> StarCluster at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/starcluster
>>
>>
>>
>> _______________________________________________
>> StarCluster mailing list
>> StarCluster at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/starcluster
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20151117/0a9317db/attachment.html