EC2 m3.large in US East

[ssanner]

Folks,

We have a report that m1.large instances can no longer launch in the AWS US East zone.

Can others confirm?  If true, this means we need an alternative.

Would everyone be OK with an m3.large instance?  The specs are a little different:

  http://aws.amazon.com/ec2/instance-types/

**IF YOU CANNOT run with a m3.large instance, please post to this list now to discuss.

For uniformity of computation and network lag, everyone should use the same instance type in the same AWS zone.

Thanks,

Scott

[Nicolas Drougard]

Hi Scott,

We are OK with an m3.large instance + AWS US East zone (N.Virginia).

Bests,
Nicolas

[Scott Sanner]

From Andrey Kolobov:

>  I discovered that there is a way to choose an m1.large instance by selecting "all generations" as opposed to 

> "current generation" (which is the default) right above the instance type selection table.

In this case, we'll stick with the m1.large as long as everyone can run it.  -Scott

--
You received this message because you are subscribed to the Google Groups "IPPC 2014 (DISCRETE TRACK)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ippc-2014-discr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marek Grzes]

On 10/06/14 01:46, ssanner wrote:

Folks,

We have a report that m1.large instances can no longer launch in the AWS US East zone.

That's true. I cannot see m1.larger either (it was available at the time when I was compiling our EC2 manual https://cs.uwaterloo.ca/~mgrzes/IPPC_2014/IPPC_2014_Amazon_EC2_Setup.pdf). For that reason our competition servers will run m3.large. I would encourage all teams to use m3.larger as well.

Can others confirm?  If true, this means we need an alternative.

Would everyone be OK with an m3.large instance?  The specs are a little different:

  http://aws.amazon.com/ec2/instance-types/

**IF YOU CANNOT run with a m3.large instance, please post to this list now to discuss.

I created one m3.large in Virginia Region yesterday and it worked fine. I've just checked another server, and it seems to be possible to create more m3.large instances from our UW network.

Please all try to create your m3.large instances in the Virginia Region.


Cheers,
Marek

For uniformity of computation and network lag, everyone should use the same instance type in the same AWS zone.

Thanks,

Scott