Re: Latest new about Juju master branch - upload-tools obsoleted

I discovered another trick that works: set the streams and urls to invalid values in your bootstrap config. This will force Juju to use an already compiled jujud in your $PATH. For example, bootstrap --config with: image-metadata-url: http://localhost image-stream: nope agent-metadata-url:

Re: Latest new about Juju master branch - upload-tools obsoleted

Just a note, because it wasn't clear to me - there are a couple cases where the automatic upload tools won't do what you want, if you use a version of juju you built locally. If you're not a developer or someone who builds juju from source, it's safe to ignore this email. *1. If the version of

Re: Latest new about Juju master branch - upload-tools obsoleted

On 2016-08-15 08:27 AM, Ian Booth wrote: > Please let me know if there's any questions. --upload-tools is still supported > but will be removed soon. Has --upload-tools already been removed? The lack of it appears to be breaking gui tests:

Re: Latest new about Juju master branch - upload-tools obsoleted

This seems really nice, but I'm slightly wary of "magic" heuristics like this. In particular, bootstrapping can take a while and I have wasted plenty of time in the past trying to find bugs but having bootstrapped using the wrong binary... So I'm hoping this new feature provides at least these

Re: Latest new about Juju master branch - upload-tools obsoleted

OK, I think I've got it now. On 16/08/16 15:19, Ian Booth wrote: On 16/08/16 12:58, Tim Penhey wrote: On 16/08/16 10:50, Ian Booth wrote: On 16/08/16 03:09, Nate Finch wrote: Ian, can you describe how Juju decides if it's running for a developer or an end user? I'm worried this could

Re: Latest new about Juju master branch - upload-tools obsoleted

On 16/08/16 12:58, Tim Penhey wrote: > > > On 16/08/16 10:50, Ian Booth wrote: >> >> On 16/08/16 03:09, Nate Finch wrote: >>> Ian, can you describe how Juju decides if it's running for a developer or >>> an end user? I'm worried this could trip people up who are both end users >>> and happen

Re: Latest new about Juju master branch - upload-tools obsoleted

On 16/08/16 03:09, Nate Finch wrote: > Ian, can you describe how Juju decides if it's running for a developer or > an end user? I'm worried this could trip people up who are both end users > and happen to have a juju development environment. > It's not so much Juju deciding - the use cases

Re: Latest new about Juju master branch - upload-tools obsoleted

Ian, can you describe how Juju decides if it's running for a developer or an end user? I'm worried this could trip people up who are both end users and happen to have a juju development environment. On Mon, Aug 15, 2016 at 11:29 AM Mark Shuttleworth wrote: > On 15/08/16 08:27,

Re: Latest new about Juju master branch - upload-tools obsoleted

On 15/08/16 08:27, Ian Booth wrote: > So if you pull master you'll no longer need to use upload-tools. > Juju will Do the Right Thing*, when you type: Thanks Ian, this is a lovely simplification. Mark -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at:

Latest new about Juju master branch - upload-tools obsoleted

So if you pull master you'll no longer need to use upload-tools. Juju will Do the Right Thing*, when you type: $ juju bootstrap mycontroller aws|lxd|whatever or $ juju upgrade-juju *so long as your $GOPATH/bin is in your path (as a developer). 1. As a user, you bootstrap a controller using a