Juju 2.3.2 is released

2018-01-16 Thread Christian Muirhead
Juju 2.3.2 has arrived! This is primarily a bug fix release. ## Critical bugs fixed. Among the bugs fixed two were considered critical. - 1737058 `network-get` fails to find valid configs - 1738728

Weekly Development Summary

2017-06-09 Thread Christian Muirhead
Hi everyone - It's Friday again! That means it's time for another Juju development summary, and then the weekend. Juju 2.2-rc1 was released on Tuesday and rc2 was released today with some additional bug fixes, and support for loading credentials directly from the Azure CLI [0]. Team focus has

Fwd: Big memory usage improvements

2016-10-13 Thread Christian Muirhead
Oops, meant to reply-all. -- Forwarded message - From: Christian Muirhead <christian.muirh...@canonical.com> Date: Thu, 13 Oct 2016, 09:26 Subject: Re: Big memory usage improvements To: Katherine Cox-Buday <katherine.cox-bu...@canonical.com> On Wed, 12 Oct

Re: Big memory usage improvements

2016-10-13 Thread Christian Muirhead
On Wed, 12 Oct 2016, 21:39 Menno Smits, wrote: > Interestingly the MongoDB memory usage profile is quite different as well. > I'm not sure if this is due to Christian's improvements or something else. > Thanks Menno! One of the fixes was a state.State instance being

Re: Juju 2.0-rc3 is here!

2016-10-07 Thread Christian Muirhead
It indicates that that unit is the leader for the application. It's a bit academic in the status you pasted, since each application only has one unit, but I can see it being useful if you had scaled out a bit. Cheers, Christian On Fri, Oct 7, 2016 at 5:59 PM Adam Israel

Re: The CI build time continue to rise alarmingly

2016-06-08 Thread Christian Muirhead
Hi Torsten - That fix shouldn't have increased build times unless we also changed the test run to be against Mongo 3.2. If builds are still against 2.4 then the change will have made them slightly faster (because we only drop and recreate the database at the suite level). I don't think we've

Re: Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

2016-05-18 Thread Christian Muirhead
a serious problem that is being ignored. > > On Wed, May 18, 2016 at 7:32 PM, Christian Muirhead > <christian.muirh...@canonical.com> wrote: > > WiredTiger is *much* slower at creating and dropping indexes and > > collections. I haven't worked out why that is, other than doing so

Re: Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

2016-05-18 Thread Christian Muirhead
run). On Wed, May 18, 2016 at 10:36 AM Michael Hudson-Doyle < michael.hud...@canonical.com> wrote: > On 18 May 2016 at 21:32, Christian Muirhead > <christian.muirh...@canonical.com> wrote: > > WiredTiger is *much* slower at creating and dropping indexes and > > col

Re: Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

2016-05-18 Thread Christian Muirhead
ain? > On 18 May 2016 09:51, "Christian Muirhead" < > christian.muirh...@canonical.com> wrote: > >> >> >> On Wed, May 18, 2016 at 2:04 AM David Cheney <david.che...@canonical.com> >> wrote: >> >>> 100x more webscale >