[00:53] wallyworld: thanks for changes, looking at your PR again now [00:53] ta [01:14] wallyworld: not for right now, but we'll need to figure out how to incorporate the CAAS hook tool names into "juju help-tool" [01:14] yeah [02:47] wallyworld: just about to run QA again, can you please take a look at https://github.com/juju/juju/pull/8131 when you're free? [02:47] sure [03:28] wallyworld: I don't see the typo [03:29] wallyworld: were you thinking s/machine/unit/ ? this helper is used by both TestDestroyMachine... and TestDestroyUnitHostMachine... - it's more about destroying the machine than the unit [03:30] axw: i realised i misread the code - i deleted the comment [03:30] okey dokey [03:50] wallyworld: https://github.com/juju/juju/pull/8132 [03:54] thumper: looking in a bit [03:55] ack [04:58] wallyworld: when you're free, I'm ready to chat about next steps [04:59] axw: ok, give me 5 [05:01] * axw goes to make coffee [05:16] axw: free now, standup HO? [05:16] wallyworld: yup, brt [05:30] Bug #1733847 changed: same ip got assigned to two different container [06:41] wallyworld: snap CDN is buggered atm it seems, so blocked on getting k8s installed. I'm going to write some unit tests for worker/caasoperator, and do a little refactoring to bring it more in line with newer workers [06:41] ok, sgtm === frankban|afk is now known as frankban [08:38] wallyworld: https://github.com/juju/juju/pull/8134 - snaps are back, but gotta make dinner. bbl [08:38] ok [09:41] wallyworld: to avoid spreading juju bits across the image, can we put jujud at /var/lib/juju/tools/jujud? then we can still derive from data-dir [09:41] axw: that sounds ok to me [09:42] wallyworld: alternatively we could put it in /var/lib/juju/tools//jujud as we do now, but makes the image build step a little more complicated. maybe worth it for consistency? [09:43] but to we really need that since images are not updated but replaced [09:44] wallyworld: we don't. I'm just thinking the fewer differences the better [09:44] wallyworld: to avoid having if-iaas-this-else-if-caas-that [09:44] there's lots of other difference already IMO [09:44] * axw shrugs [09:45] this caas operator is different code really [09:45] I'll make it a static path for now, we'll see how it goes [09:45] yeah we can always revise [09:45] start simple [09:51] wallyworld: pushed a change, PTAL [09:51] righto [09:53] axw: i don't think applocationName is used in waitForApplicationActive() [09:53] indeed [09:54] fixed [09:56] axw: also, we don't really need Application attr on worker Config - it's just used to print an error message inside the worker - could easily be done by the NewWorker caller [09:56] wallyworld: I imagine we'll want to use it later on [09:56] passing to the API [09:57] yeah could do [09:57] ok [09:57] axw: lgtm, thanks for extra changes, i wanted to do clock etc but ran out of steam [09:58] wallyworld: thanks [11:15] balloons: veebers: The bot failed to comment on my PR again. [11:15] axw: did the bot work correctly on your PR? [11:16] on mine I had failed to run 'go fmt' and that seemed to cause the bot to reject the PR, but fail to actually update the github comment. [13:09] wallyworld: since I'm going to need an API for getting the charm URL anyway, I'm going to add one with the SetStatus API (unless you already started on it?) [13:09] nope, not started yet [17:09] jam, https://github.com/juju/juju/pull/8128? [17:10] balloons: yeah, it had a 'go fmt' issue, and that clearly failed the test suite, but didn't report back to the PR [17:10] so I did a Rebuild directly [17:12] jam, is this just the card we have about go fmt not returning non-zero? [17:12] balloons: well, it failed in the builder [17:12] it just didn't reply to the PR which meant a follow up "$$merge$$" ddn't work [17:14] the $$merge$$ bot really needs replaced, but is blocking on pipelines allowing merges. It's behavior shouldn't have changed in all the time it's been running. [17:14] so that's interesting it wouldn't accept another $$merge$$ === frankban is now known as frankban|afk [17:50] jam, do you have anything pressing to discuss? I could use the time today iif not [17:51] balloons: nope, I'm half falling asleep anyway. [17:56] jam, :-) [19:04] how might I build a charm to deploy Windows 10? [19:05] on MAAS [20:15] Is there a mergebot on https://github.com/juju/description or someone has to do it manually? [20:22] wpk: I don't think it has been set up yet [20:22] I can click the button if necessary [20:23] thumper: please do [20:23] * thumper takes a look [20:24] wpk: sorry, the work isn't right [20:25] since you are adding a field, you need to bump the serialisation version [20:25] the schema package is very strict [20:25] * thumper looks for an example [20:26] wpk: take a look at this work wallyworld did https://github.com/juju/description/pull/25/files [20:27] fixing [20:31] wpk: what is going to happen on an import if there is no default gateway? [20:32] is it an expected value in 2.3? [20:32] thumper: we only do something if IsDefaultGateway is set to true [20:32] thumper: since default is false -> we won't do anything [20:33] but the code doesn't rely on there being one with default gateway set? [20:34] no [20:34] good [20:34] * thumper out [20:51] Anyone else with powers to merge juju/description? [21:12] balloons: ? [21:12] wallyworld: ? [21:13] wpk, pr? [21:14] https://github.com/juju/description/pull/30/files === petevg_afk is now known as petevg [21:32] wpk: done [21:32] balloons: we having release standup? [21:41] wallyworld: danke schon [21:48] wpk: with the SUperSubnets() PR, looks ok but we need unit tests === admcleod_ is now known as admcleod [22:01] wallyworld: recheck plz. [22:02] looking [22:03] wpk: awesome, ty [22:14] wallyworld: good call on the upgrade step - what version should I put that in for? 2.3.1 [22:14] ? [22:14] babbageclunk: otp, give me 5 [22:14] wallyworld: no rush [22:36] wallyworld: https://github.com/juju/description/pull/31 , too late here.. [22:36] wpk: looking [22:37] wpk: done [22:39] babbageclunk: the upgrade step version matches what juju version the code lands in, so it will be 2.4 [22:39] oh of course it's 2.4, thanks [23:58] wallyworld: did you have any trouble with kubernetes-core and the kube-system pods not coming alive? [23:58] no [23:58] it took a few minutes [23:59] wallyworld: I left it over night :) somethings borken [23:59] I'll blow it away and see if it happens again [23:59] hmmm