Comment 2 for bug 1215948

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

On 2013-08-23 18:33, Matthew Wedgwood wrote:
> I second Nick's request, and also point out that the provider
> might be an appropriate indicator of whether the tools should be
> collected from AWS. Is the behavior the same on Azure or HP Cloud?
>
> My vote would be behind --upload-tools being the default, with a
> convenience option to use canonical-hosted buckets.
>

The tools on your local system are generally not valid for all
permutations of target machines. (i386, amd64, precise, quantal,
raring, saucy).

It is intended that you would get a copy of the tools into your local
cloud from some other location. (see 'juju sync-tools' and the
- --source parameter if you want to copy them manually from a local disk
copy.)

I understand not wanting "juju bootstrap" to automatically grab them
for you. "--upload-tools" will work in a subset of cases (where the
platform you are running on matches exactly the platforms of all
machines you will be running).

Without some sort of tools copying, your environment wouldn't have
been able to bootstrap anyway, so I'm not sure failing at trying to
copy tools is worse than failing at not having tools available.

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

iEYEARECAAYFAlIZlokACgkQJdeBCYSNAAM+CgCgjHZIogvkLnN58HWx8IsMDVMv
CSMAoJ0cPZeJO8uK3ZgzeJ2Qi1/voJOQ
=5zXz
-----END PGP SIGNATURE-----