constraints call notes/proposals/sync

[John Arbash Meinel]

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

...

> 
> If, on the other hand, it's an ec2-only constraint, I am concerned
> that to implement is is implicitly to drop flavor support in
> openstack, in favour of a provider-specific measure that will make
> it harder to implement a sane openstack variant (we can't just have
> os-type, that can vary like anything, and suffers exactly the same
> problems as any global instance-type measure would).
> 
> I presume that there's a third interpretation I haven't spotted?

I do think this is what he meant. And I think the idea is that while
you have ec2-type, you might also have openstack-flavor=XXX.
In which case your driving scripts would do:

juju bootstrap
-
--constraints='ec2-type=m1.tiny,google-type=n1.medium,openstack-flavor=m1.notsotiny'

And then the constraints that don't apply to the provider just get
ignored (or logged-but-ignored). And you don't have to expose directly
in the script which cloud it is running on.

John
=:->

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

iEYEARECAAYFAlETZ08ACgkQJdeBCYSNAANGMQCffja2+72PEQ092CfgUiVWY2kD
fXcAnRpLHl3PBd5nCFigmLI6MM8HgXp5
=/4p7
-----END PGP SIGNATURE-----