[00:04] <babbageclunk> anastasiamac: ah, I missed that
[00:08] <thumper> timClicks: well, since we are stopping testing against 1.9 there is a chance we'll miss something
[00:08] <thumper> I'd rather say people need to go through juju 2.5 or 2.6 in order to upgrade their maas
[02:43] <wallyworld> babbageclunk: if you have a moment at some point https://github.com/juju/juju/pull/10548
[02:48] <babbageclunk> wallyworld: taking a look
[02:48] <wallyworld> ty, no rush
[03:22] <magicaltrout> random trivia question
[03:22] <magicaltrout> if you do a juju remote backup
[03:23] <magicaltrout> does it persist it somewhere on the filesystem on the server?
[03:23] <magicaltrout> if so, where is it?
[03:25] <wallyworld> magicaltrout: you talking abou the juju create-backup command?
[03:26] <magicaltrout> yeah
[03:27] <wallyworld> by default it will download it to your local client, but you can specify --keep-copy and it (I think) is stored as a blob in mongo
[03:27] <wallyworld> you can list what ones are stored in the controller via list-backups
[03:27] <magicaltrout> yeah, fair enough, plan b then
[03:28] <wallyworld> you can choose to 1. contoller copy only, 2. local copy only, 3. both
[03:28] <wallyworld> via a combination of --no-download and --keep-copy
[03:28] <magicaltrout> ironically if you just want a pool and run a backupscript over them, 1,2 and 3 aren't ideal ;)
[03:29] <magicaltrout> i'll stick juju on another box and hook up some cronjob against it
[03:30] <wallyworld> if there's a use case you want, you could post a question on discource and we can consider it
[03:30] <wallyworld> backups do need some love and attention
[03:30] <magicaltrout> ha, i won't waste your cycles on it, i just hoped the backups would land somewhere on the controller and I could just dump them to backblaze rather than the client downloading the file then doing it
[03:31] <magicaltrout> but its not a big deal
[05:41] <wallyworld> kelvinliu: got a minute for a HO?
[05:42] <kelvinliu> wallyworld: sure
[11:17] <stickupkid> CR anyone https://github.com/juju/os/pull/10?
[11:43] <manadart> stickupkid: Avin' a butcher's.
[12:02] <manadart> stickupkid: I approved it, but then made a suggestion.
[12:57] <stickupkid> manadart, i agree with said comment
[14:37] <stickupkid> rick_h, this now correctly handles the Any type https://github.com/juju/python-libjuju/pull/345
[14:43] <rick_h> stickupkid:  k, gave it a look but I have a case of not trusting my review eyes and wanting to see a test/code prove it works out.
[14:44] <stickupkid> rick_h, 100% agree... this isn't pretty as I don't have the context to why it was wired up originally like that - it seems weird
[14:45] <stickupkid> rick_h, i wonder if the assumption was that an `interface{}` would always be `map[string]interface{}`
[14:51] <rick_h> stickupkid:  so an interface an map walk into a bar...
[14:51] <rick_h> stickupkid:  no idea
[15:56] <stickupkid> rick_h, got a sec?
[15:56] <rick_h> stickupkid:  definitely
[15:56] <stickupkid> rick_h, ho
[15:56] <rick_h> omw
[20:58] <magicaltrout> hello folks
[20:58] <magicaltrout> lazy relation question
[20:58] <magicaltrout> on the far end of a connection, how do I get the network addressable name/ip at the other end?
[20:59] <magicaltrout> unit.blah
[22:53] <timClicks> magicaltrout: sorry that we haven't gone an answer to you yet
[22:54] <timClicks> magicaltrout: would you mind asking in discourse?
[22:56] <timClicks> have updated our tutorials page to be more accessible to new users and to surface up community-contributed how tos https://jaas.ai/docs/tutorials
[23:24] <wallyworld> magicaltrout: i think that's normally info that the other end is expected to put in relation data. the remote unit uses the network-get hook command to get the address info for a given binding/endpoint and shoves that in relation data for the other unit to read