A new development release of Juju, 2.0-beta15, is here!

A new development release of Juju, 2.0-beta15, is here! ## What's new? This releases addresses stability and performance issues including 29 bugs from b14 last week. Some notable ones include: * lxd containers not using configured proxy for downloading images LP 1594720

Default bootstrap machine sizes on public clouds

It's been a while since we discussed the default machine sizes to use when bootstrapping on public clouds. Now that we have multi-model controllers I'm seeing folks stress the controller a lot harder (which is good :)) and I wonder if we shouldn't up the defaults? Mark -- Juju mailing list

Re: So I wanted to update a dependency . .

On Thu, Aug 11, 2016 at 5:44 PM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > This is a simple story of a man and a simple mission. Eliminate the final > 2 dependencies that are in bazaar and launchpad. It makes juju and it's > dependencies live completely in git. A notable goal, and

Re: Some Juju CLI usability thoughts before we close 2.0

On 11/08/16 17:46, Ian Booth wrote: > > On 11/08/16 17:03, John Meinel wrote: >> On Thu, Aug 11, 2016 at 9:30 AM, Ian Booth wrote: >> >>> A few things have been irking me with some aspects of Juju's CLI. Here's a >>> few >>> thoughts from a user perspective (well, me

So I wanted to update a dependency . .

This is a simple story of a man and a simple mission. Eliminate the final 2 dependencies that are in bazaar and launchpad. It makes juju and it's dependencies live completely in git. A notable goal, and one that I desired for getting snaps to build with launchpad. I don't feel I need to explain

Re: maas in a container

Daniel, Can you show the full dump of your profile and container configs? Here's what my 'maas' profile looks like: ubuntu@beartic:~$ lxc profile show maas name: maas config: raw.lxc: |- lxc.cgroup.devices.allow = c 10:237 rwm lxc.aa_profile = unconfined lxc.cgroup.devices.allow =

Re: Uniter test failure from utils update

Thanks for the insights here. I ended up reverting the offending change, https://github.com/juju/utils/pull/203. @bogdanteleaga, my apologies for reverting, but I'm not sure how to fix with your change so I went back to something that worked. It's worth following up and figuring out how to re-land

Re: Point people to ubuntu-on-windows instead of the broken juju-on-windows?

On Thu, Aug 11, 2016 at 2:02 PM, Nate Finch wrote: > The linux ssh works so much better because we can simply run the OS's ssh > and everything Just Works, but that's not possible on Windows, so it's much > more involved to make it work (we basically have to write an

Re: Point people to ubuntu-on-windows instead of the broken juju-on-windows?

Hi Nate Thanks for your quick reply! My colleagues will just 'upgrade' to windows 10 so this doesn't really apply to us anymore but wouldn't it be easier to package putty with the windows juju client and use that as default? Writing an entire ssh client seems a bit overkill.. or is there an

Re: Point people to ubuntu-on-windows instead of the broken juju-on-windows?

Just FYI - running the juju client on Windows is 100% supported and we actively fix bugs on it all the time. I hadn't seen the particular bug you referenced about juju ssh, but that definitely seems like something we should prioritize higher. The linux ssh works so much better because we can

Point people to ubuntu-on-windows instead of the broken juju-on-windows?

Hi all Juju-on-windows is pretty broken and it doesn't seem that bugs are being fixed anymore. Wouldn't it be better to point people to Juju on "Ubuntu on windows" instead? One of my colleagues started using it and it seems to work just fine. Some show-stopping bugs in Juju-on-windows: -

Re: Uniter test failure from utils update

(or, at least, it's something like that -- the general point is that you shouldn't throw away values you don't know you don't need) On Thu, Aug 11, 2016 at 2:14 PM, William Reade wrote: > worker/uniter/operation/runcommands.go:68... uses `context.ErrReboot` to >

Re: Uniter test failure from utils update

worker/uniter/operation/runcommands.go:68... uses `context.ErrReboot` to indicate "there is a valid response value that should be handled, but we also need to queue a reboot". The change throws away the valid response. On Thu, Aug 11, 2016 at 1:47 AM, Martin Packman <

Re: Regarding Terms

Just replying publicly to confirm that this was done earlier this morning Thanks Matty On Thu, Aug 11, 2016 at 10:30 AM, Shruthima Almavar wrote: > Hi, > We have sent a request for terms creation through the terms link ( >

Regarding Terms

Hi, We have sent a request for terms creation through the terms link ( https://docs.google.com/forms/d/1sOfp0a6KLY9kqnpPeGwHv_YQJv7LEbXH1CAV-xBaMjU/viewform?edit_requested=true ) for the following charms: ibm-http-server ibm-http-plg ibm-http-wct ibm-mobilefirstserver ibm-spectrum-scale Could

Re: Some Juju CLI usability thoughts before we close 2.0

On 11/08/16 17:03, John Meinel wrote: > On Thu, Aug 11, 2016 at 9:30 AM, Ian Booth wrote: > > > A few things have been irking me with some aspects of Juju's CLI. Here's a > > few > > thoughts from a user perspective (well, me as user, YMMV). > > > > The following pain

Re: Some Juju CLI usability thoughts before we close 2.0

On Thu, Aug 11, 2016 at 9:30 AM, Ian Booth wrote: > A few things have been irking me with some aspects of Juju's CLI. Here's a > few > thoughts from a user perspective (well, me as user, YMMV). > > The following pain points mainly revolve around commands that operate on