Automatic tools-upload/sync during bootstrap

[John Arbash Meinel]

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

On 2013-10-11 10:19, Ian Booth wrote:
>> 
>> So I'd like to see what people think of this: - Keep "juju
>> bootstrap --upload-tools", but make that the only time we attempt
>> to upload during "juju bootstrap". There will not be any
>> automatic upload if tools aren't found and syncing fails.
> 
> The auto upload was added to avoid the less than user friendly
> scenario whereby people running from source could not bootstrap
> without specifying --upload-tools. My opinion is that the current
> functionaility is waranted because it makes bootstrap Just Work and
> removes a common failure path. It also unifies the bootstrap
> command for dev vs prod and consistency is good.

Actually that isn't true. It was added to help the MaaS case where
every environment needs to have the tools bootstrapped. Then Tim
noticed that in the local provider he could cheat and auto-supply
- --upload-tools and make it find the jujud next to the juju binary. And
then *you* noticed, hey why aren't we just always supplying
upload-tools when we can't find the tools we want elsewhere.

Personally, I've seen mixed results. Where bootstrap actually fails
because it can't get the tools (the MaaS case it was trying to solve
but they don't have outbound network). What *is* helped is for us
developers, but I think it "helps" in a fashion that is actually an
ultimate negative for us.

If we want 'juju bootstrap' to be grabbing the jujud next to it, then
that should *be the way* that we distribute tools. Just having it so
it is easier to test the code you're working on is not a good answer,
when it is *not* the way that we have people use Juju in production.

John
=:->


> 
>> - Remove the option to specify a tools source. If you really want
>> to do that, use juju sync-tools.
>> 
> 
> You mean tools-url in config? We need this to allow private clouds
> (and anyone else) to serve the tools using an arbitary http server
> (or from a shared directory). In any case, sync-tools only copies
> to the private storage (for ec2 and openstack at least)  and such
> tools are not generally available to anyone else. The tools-url is
> intended to be configured with a shared public location from which
> to get tools. So for the above reasons, we need to keep this
> option.
> 
> 

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

iEYEARECAAYFAlKLCr4ACgkQJdeBCYSNAAP1gwCdFun5kHD0HvQETkdoQJwMq6rp
6X8AoKR8VytV0TarxNlbGhcF8IsTHX1n
=6SIQ
-----END PGP SIGNATURE-----