How do I launch and m1.medium on AWS?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

...

> 
> Both EC2's instance type and MaaS tags are exposed through generic 
> constraints (type and tags respectively) that are intended to be 
> implemented in provider-specific ways.  Right now they are just
> ignored by providers that don't support them (so you can do
> tags=foo when running against EC2, and it'll just act as if the
> constraint wasn't there).  So trying to add-machine --constraints
> type=m1.large against maas will actually give you any random
> machine on maas.
> 
> I see three possible behaviors when you specify a constraint that
> is not supported by the provider you're working against:
> 
> 1.  It could be ignored (this is what we do now) 2.  It could cause
> the command to simply fail immediately. 3.  We could try to make
> our best guess at what the user means.
> 
> I'm not a big fan of #3, either of the other behaviors are fine, in
> my opinion.
> 
> In theory we could translate EC2 instance types into lists of
> other constraints (cpu-cores, memory, etc), and use those lists of
> constraints against other providers.... so effectively that would
> work like "hey, give me something that looks like an m1.large on
> this provider"... but I'm not sure if that would be more surprising
> than helpful.
> 
> -Nate

There are a few issues here. At some point we will want to support
instance-type in Openstack where I believe they are called flavors,
and they are site-specific. (eg Canonistack *has* an m1.tiny, but HP
Cloud calls them standard.medium)

We've gone around that discussion a *lot* about how you specify a
value that is site-specific. Do you need a site-specific key?
(ec2-instance-type=XYZ) Do you just use cloud specific values and
require the user to adjust their script (if $CLOUD == "EC2":
TYPE="m1.tiny" elif .. TYPE="standard.small"; juju deploy
- --constraints type=$TYPE)


We talked about supporting a potential list and we just pick out which
one might fit, but Canonistack and EC2 both define an "m1.tiny" that
may or may not match well enough (and we don't provide a way to be
more specific without just site specific meaning).

Anyway, I think we ended up with values are cloud-specific and scripts
need to take that into account, but it is probably worth discussing
again in SFO.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJWj/QACgkQJdeBCYSNAAPvUACgulsXItCO9cUah4c/826ebCLZ
1wMAoIKSY2LCpxHTlaZcmuHKNriEDyvW
=92mD
-----END PGP SIGNATURE-----