Automatic tools-upload/sync during bootstrap

[Andrew Wilkins]

On Fri, Oct 11, 2013 at 2:19 PM, Ian Booth <ian.booth at canonical.com> 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.
>
> >  - 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.
>

I was referring to "juju bootstrap --source=<local-path>" for syncing.
tools-url should definitely stay.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20131011/b3f3600f/attachment.html>