Generating environments.yaml

[John Arbash Meinel]

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

ATM, it seems most people start using juju by running "juju bootstrap"
to get an environments.yaml generated, and then hacking that to make
it work.

It seems like we'd like to have a command that generates
'environments.yaml' from some sort of template, which can fill it out
with reasonable starting state. (A random password for admin-secret, a
random bucket for uploading tools to, etc.)

Do people like the idea of a command like "juju generate-environment"?

1) Is it worth pursuing the design of this? Or is it going to be
rejected from the start.

2) Assuming worthwhile, do we have a good name for it?

3) Would it generate an environments.yaml that had all possible
providers, or would you supply the provider as a commandline parameter.

4) Would we be able to detect possible providers based on environment
variables? (e.g. You have OS_USERNAME set, so I'll generate the
openstack version.)

5) Especially for stuff like canonistack, would it be worth generate a
canonistack specific environment, rather than a generic openstack one
(vs hp, vs rackspace, etc.)

Thoughts?

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

iEYEARECAAYFAlD+hI8ACgkQJdeBCYSNAAN9gwCdEA95URg2Yy2/2fXkTL3X0DoC
OM8AoNc9Kons+OjFU0jBB7/oQCVlZqCq
=3Wot
-----END PGP SIGNATURE-----