All, I'm in the process of landing the following MP which removes the --source flag from "juju bootstrap"; this should go into the release notes. As discussed, you can still use --source with sync-tools. https://code.launchpad.net/~axwalk/juju-core/lp1236691-null-provider-default-series-take2/+merge/190032
In case you missed other discussions: the Environ interface's Bootstrap method no longer takes a set of possible tools, and is now responsible for locating tools itself. The primary driver for this is manual provisioning, where the series of the machine dictates the tools, and not the other way around like with the other providers. Cheers, Andrew On Tue, Oct 15, 2013 at 9:56 AM, Andrew Wilkins < [email protected]> wrote: > On Fri, Oct 11, 2013 at 2:19 PM, Ian Booth <[email protected]>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. >> > > I'll leave it in, though I think it will have to change slightly to drop > the automatic uploading of tools for series specified through --series. > That can still be handled by "juju bootstrap --upload-tools". > > I'm readying a CL now. Took a while to get the tests right. > > Cheers, > Andrew >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
