Re: Request to support to work with Juju

2015-04-30 Thread Marco Ceppi
Hello, are you using the local provider? If so it can take several minutes to seed the initial download of the cloud image. You can find if the image was downloaded by checking /var/cache/lxc/cloud-* where * is precise, trusty, or the series you're trying to deploy. Images are downloaded only when

Request to support to work with Juju

2015-04-30 Thread dinesh.senapaty
Hi, I have been working on Juju for last 2 weeks. There are some blockages while working on it like: 1.In juju bootstrap. It is not downloading the disc image itself. But when I check juju status, it is showing machine-0 (started state). 2.And when I try to deploy any service, it adding the

Re: previously valid amazon environment now invalid?

2015-04-30 Thread Ian Booth
Right now, the default tabular output is behind a feature flag because it's experimental. We still need to decide how to allow users to have that output by default without the feature flag, but also without breaking 1.18 script compatibility. The best option IMO for this case is an env variable on

Re: previously valid amazon environment now invalid?

2015-04-30 Thread roger peppe
On 30 April 2015 at 11:55, Ian Booth ian.bo...@canonical.com wrote: Right now, the default tabular output is behind a feature flag because it's experimental. We still need to decide how to allow users to have that output by default without the feature flag, but also without breaking 1.18

Re: previously valid amazon environment now invalid?

2015-04-30 Thread Nate Finch
I would say the exact opposite. We *cannot* sacrifice the usability and reliability of the product for all our future users just to keep a few current users from having to update their scripts ever. I am sure there will come a day when we decide that there is a change that makes the client

Re: previously valid amazon environment now invalid?

2015-04-30 Thread Michael Hudson-Doyle
I don't want to bore on and on about this, but one thing. On 30 April 2015 at 22:06, Nate Finch nate.fi...@canonical.com wrote: If someone needs 1.18 CLI compatibility, they can use 1.18. It's that simple. It's not that simple to do that though, as long as new versions of juju go into

Re: previously valid amazon environment now invalid?

2015-04-30 Thread roger peppe
At the Nuremberg sprint, I saw a demo of juju status that produced tabular format by default. I'm guessing that this issue means that can never actually be enabled. Although... it could be done backwardly compatibly (with a required environment variable or configuration file setting) and perhaps

Re: previously valid amazon environment now invalid?

2015-04-30 Thread Ian Booth
On 30/04/15 21:04, roger peppe wrote: On 30 April 2015 at 11:55, Ian Booth ian.bo...@canonical.com wrote: Right now, the default tabular output is behind a feature flag because it's experimental. We still need to decide how to allow users to have that output by default without the feature

Re: previously valid amazon environment now invalid?

2015-04-30 Thread Richard Harding
On Thu, 30 Apr 2015, Nate Finch wrote: If someone needs 1.18 CLI compatibility, they can use 1.18. It's that simple. We're maintaining API compatibility for just this reason. If they don't want the binary to change, they shouldn't update it (or should just rename it to juju-1.18 or

Juju stable 1.23.2 is released

2015-04-30 Thread Curtis Hovey-Canonical
# juju-core 1.23.2 A new stable release of Juju, juju-core 1.23.2, is now available. This release replaces version 1.22.1. ## Getting Juju juju-core 1.23.2 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/stable Windows

Re: Juju stable 1.23.2 is released

2015-04-30 Thread Antonio Rosales
\o/ Thanks for the hard work on this. I can't wait to give all these new features a spin. -Antonio On Thu, Apr 30, 2015 at 8:41 PM, Curtis Hovey-Canonical cur...@canonical.com wrote: # juju-core 1.23.2 A new stable release of Juju, juju-core 1.23.2, is now available. This release replaces