[01:30]  * thumper loads up his controller
[01:30] <thumper> hopefully this won't actually kill my laptop
[01:30] <thumper> I'm trying to replicate the death spiral we see with some controllers with lots of models
[01:36] <hml> thumper: ha, you’re brave?
[01:37] <thumper> well... I'm up to 300 models and 60 total units
[01:37] <thumper> starting to see rises in txns.log reads
[01:37] <thumper> since I'm on an SSD, no doubt my profiling will be different
[01:37] <thumper> but slowly adding stuff to see it get stressed
[01:37] <hml> wallyworld: i pushed the pr changes, but there is something wrong with the tests, but real world does what it should on packages.
[01:37] <hml> wallyworld: i’m EOD, look at tests in the morning
[01:38] <wallyworld> ok, ty
[01:57] <thumper> currently: goroutine profile: total 166500
[01:58] <thumper> axw: the new hook execution locking behaviour is 2.3 not 2.2.6 right?
[01:59] <axw> thumper: correct
[02:00]  * thumper nods
[02:00]  * thumper slowly adds more models and units
[02:05] <thumper> perhaps unsurprisingly, my machine is starting to get a little sluggish
[02:21] <thumper> wallyworld: I've got a problem, got a minute?
[02:21] <wallyworld> sure
[02:21] <thumper> 1:1 HO
[02:25] <mwhudson> an overloaded controller _and_ hangouts? brave man :)
[02:42] <axw> wallyworld: the state.Unit.ConigSettings method adds defaults, the application method does not
[02:42] <axw> ConfigSettings*
[02:42] <wallyworld> axw: yeah, just discovering that
[02:43] <wallyworld> just otp with tum
[03:08] <cmars> i'm running into this bug with the manual provider: https://bugs.launchpad.net/juju/+bug/1736582
[03:08] <mup> Bug #1736582: Cannot bootstrap manual provider with Juju 2.2.6 <juju:New> <https://launchpad.net/bugs/1736582>
[03:08] <cmars> is there a workaround?
[03:33] <thumper> hmm...
[03:34] <thumper> when I restarted the controller
[03:34] <thumper> it would have hit the provider asking for machines for each model in very short order
[03:35] <thumper> starting all the provisioners in parallel has the potential to DDOS the provider
[03:35] <thumper> which is what we did for lxd
[03:49] <wallyworld> oops, we should fix that
[03:50] <wallyworld> thumper: i would expect model migrations to copy across charms - it that something that is done out of band? or is it in the export yaml?
[03:50] <wallyworld> i'm guessing out of band?
[03:51] <wallyworld> or is that just resources that gets streamed across
[04:08] <babbageclunk> wallyworld: charm binaries are done out of band - they're not in the export yaml
[04:12] <wallyworld> babbageclunk: thanks. so that means we potentially have a situation for a short time where an application has an orphaned charn reference. do we not mark the model as ready until all blobs are copied?
[04:17] <babbageclunk> wallyworld: that's right - the binaries (agents, charms and resources) are transferred in the import phase, and the model isn't marked as active until the success phase (when all the agents are switched over)
[04:17] <wallyworld> babbageclunk: thanks! i need to update a test then due to to a change i'm making
[04:38] <babbageclunk> wallyworld: no worries (he says, too late)
[04:38] <wallyworld> never too late
[04:38]  * babbageclunk still has time, it's never to late to change his mind, it's - never - too late - to change his mind
[05:15] <wallyworld_> axw: for when you are free https://github.com/juju/juju/pull/8179
[05:15] <axw> sure, just finishing up my PR then will take a look
[05:15] <wallyworld_> no rush
[05:55] <axw> wallyworld: https://github.com/juju/juju/pull/8180
[05:55] <wallyworld> axw: looking. i'm just pushing a change to fix a feature test failure
[05:55] <axw> okey dokey
[05:56] <wallyworld> done
[05:56] <wallyworld> axw: our test had a comment saying "this is wrong" referring to the source attr value, but it wasn't fixed, just a comment left behind
[05:57] <axw> wallyworld: lol :/
[05:57] <wallyworld> yeah
[05:58] <axw> wallyworld: so we don't know who owns the juju namespace?
[05:58] <wallyworld> axw: no, "they" are trying to find out
[05:58] <wallyworld> no one knows
[05:58] <axw> ok
[05:58] <wallyworld> axw: did you use the latest version of my charm? i added extra config attrs which are set in the pod spec
[05:59] <axw> wallyworld: nope, and I hacked up the charm a bit to set the spec
[05:59] <axw> maybe yours does that now?
[05:59] <wallyworld> yeah, since yesterday
[05:59] <wallyworld> i'll test once all this lands
[09:53] <jam> axw: did you see bug #1729880, someone is wanting to run a patched version of Juju but it is in a multi-architecture deploymente
[09:53] <mup> Bug #1729880: juju 2.2.4 and 2.2.6 actions dissappear when state is changed from running to complete <juju:Fix Committed by ecjones> <https://launchpad.net/bugs/1729880>
[09:53] <jam> I thought you had a script that would allow cross-compiling and uploading alternative agent binaries.
[09:54] <jam> fwiw, all he really needs is the controller to be patched, he could use official binaries for the rest of the agents (I think).
[09:54] <jam> but probably our bug about an upgraded controller creating new units/machines with the *controller* agent version rather than the *model* agent version.
[09:54] <axw> jam: I didn't. stepping out shortly, but I'll be back later to respond
[09:55] <axw> jam: FYI, it's https://github.com/axw/juju-tools
[09:55] <jam> axw: have a good night
[12:04] <anastasiamac> wallyworld: ping
[12:09] <wallyworld> yo
[12:14] <anastasiamac> wallyworld: pm'ed
[17:45] <balloons> hml, can I get a +1? https://github.com/juju/juju/pull/8182
[18:05]  * hml looking
[18:07] <hml> balloons: lgtm
[21:17] <babbageclunk> thumper: ping? Do you have a moment for some advice?
[21:17] <thumper> babbageclunk: sure
[21:18] <babbageclunk> thumper: in 1:1?
[21:18] <thumper> yep
[22:02] <wallyworld> hml: pop into stand up HO? just want to touch base about the config stuff
[22:02] <hml> wallyworld: on my way