[04:20] tlm: or hpidcock: or kelvinliu: a small constraints PR https://github.com/juju/juju/pull/12020 [04:27] wallyworld: looking [04:45] wallyworld: got this pr for adding priority and priority, could u take a look plz https://github.com/juju/juju/pull/12022 thanks [04:46] i cam [04:46] also tested updateStrategy [04:49] kelvinliu: lgtm, tyvm [04:51] wallyworld: as i can see, i tested updatestrategy working as expected, im not sure why cory got that parsing error, probably he wasn't using 2.8+? [04:51] kelvinliu: yeah, i believe he was using 2.8.1 or something [05:14] tlm: https://github.com/juju/juju/pull/12015 got this pr for caas firewaller worker for embedded apps, there are a few todos in the pr will be implemented in following prs, could u take a look plz? thanks [05:25] looking [05:41] kelvinliu: lgtm with a question about the api calls [05:44] wallyworld: right, I will change the CharmInfo(url string) to CharmInfo(appName string) [05:45] ty [05:46] thx for reviewing [08:02] I'm trying to wrap my head around Juju: is Juju Charmed Kubernetes? Why would I want Juju over microk8s? Juju can consume microk8s to make a Juju cloud but I don't know specifically why I would want to do this. "A cloud is a target that Juju knows how to manage workloads for. " But Kubernetes is already a tool for managing workloads across pods and nodes. [08:02] It looks like Charms are equivalent to Helm Charts. Is this a fair assumption? [08:24] that's a new one: `Create instance: Invalid devices: Device validation failed "eth1": Invalid value for device option "mtu": Out of MTU range (1280-9202) "9214"` [10:03] manadart, fixes the documentation issue https://github.com/juju/juju/pull/12023 [10:04] stickupkid: Nice. [10:04] not like me to miss documentation :| [10:30] stickupkid: yet another one... cursed yaml! https://github.com/juju/bundlechanges/pull/70 [10:46] stickupkid: small fix for an NPE in charm that I discovered while testing: https://github.com/juju/charm/pull/320 [10:55] stickupkid: Small one - https://github.com/juju/juju/pull/12024. achilleasa, having trouble with my Microstack; wanted to get this one up before a reboot. Be back on your review presently. [10:56] manadart: did you get it to work out of the box with snap? [10:56] I had to use the edge with --devmode and add an ip to get it to init [10:57] achilleasa, https://github.com/juju/juju/pull/11253/files#diff-a86032d7aeab77815b81f23cdfb46921 [10:58] stickupkid: I also had to "ip add X 10.20.20.1" to allow it to find rabbit [11:11] achilleasa: Yeah, I had the same issue. No change from when it was last working, but I lost the device addresses. [11:12] Then I hung on configuring the bootstrap machine... [11:12] Back up all fresh, see how it goes. [11:16] manadart: if you set up spaces and stuff please also try the last step in the QA (moving subnets) [11:17] achilleasa: Yeah, I was also going to delete a space. How would that go? [11:22] it should also work because the space-id in the subnets collection will change [11:22] and it will trigger a refresh of the rules [12:44] stickupkid: just pushed the PR for including expose settings in diff-bundle output. If you 've got some spare time can you take a look at https://github.com/juju/juju/pull/12025? [12:44] won't be till after standup tbh [12:45] not in a rush. just wanted to get all remaining chunks of work up for review today as next week I won't be able to work on this [12:46] that's the last PR though. Now I need to write a discourse post about it :D [13:29] manadart, fixes your issue with acceptance tests https://github.com/juju/juju/pull/12026 [13:44] Quick review of 2.8 into develop ? https://github.com/juju/juju/pull/12027 === kirkland is now known as Guest82000 [14:35] hml, so I've gone back to juju 2.0 and .Update has never been used to set a charm 4ddfc7da4fa771621e5f2a87492e1c6e6f068675 [14:36] hml, so it was probably used for something, but not sure what tbh [14:36] hml, maybe future planning? === tamas_erdei is now known as terdei [14:40] stickupkid: no idea…. maybe it was a juju 1 ism? [14:40] hml, I just wanted to be sure, but we're all good [14:41] stickupkid: +1 [14:47] stickupkid: have we done any upgrade juju testing on the charm origins? [14:47] hml, not for a long time [14:47] hml, we should do that [14:48] stickupkid: same thoughts [14:49] hml, in theory https://github.com/juju/juju/blob/develop/state/upgrades.go#L3108 [14:49] :-)