[00:39] <xavpaice> thumper, are you aware of the 'situation' we have at Cisco with the failed juju upgrade there?
[00:48] <thumper> xavpaice: a saw an email from elmo
[00:48] <thumper> and that there is a situation
[00:48] <thumper> did you want to discuss?
[00:48] <xavpaice> just realised in the wrong channel, but yes
[01:19] <timClicks_> wallyworld: what do you think of moving example/poc charms from ~juju to an account like ~example-charms?
[01:19] <timClicks_> cs:~juju/mariadb-k8s looks like it's a charm that's officially supported/endorsed
[01:20] <timClicks_> because it's so closely linked to the official account
[01:35] <wallyworld> timClicks_: i can see merit in that. once we move to the new charm store it will be a flat namsapce so it sort of becomes moot. given that's happening this cycle not sure it's worth the effort to move stuff right now?
[02:15] <bayar> Hi Everyone
[02:16] <bayar> Please someone help me with this error :
[02:16] <bayar> ceph-osd/0*               blocked No block devices detected using current configuration
[02:18] <bayar> When I ssh to the cephalopods-odd/0 server
[02:18] <bayar> ubuntu@s3:~$ lsblk
[02:18] <bayar> NAME              MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
[02:18] <bayar> sda                 8:0    0 136.1G  0 disk
[02:18] <bayar> └─sda1              8:1    0 136.1G  0 part
[02:18] <bayar>   └─vgroot-lvroot 253:0    0 136.1G  0 lvm  /
[02:18] <bayar> sr0                11:0    1  1024M  0 rom
[02:42] <timClicks_> wallyworld: it won't be moot, because the charm's webpage is more important that its url slug
[02:42] <timClicks_> it will still look like they're official charms published by juju
[02:44] <timClicks_> bayar: what does the output of "juju config ceph-osd osd-devices" say?
[03:40] <lucidone> timClicks_, wallyworld: for what it's worth, my impression as a new member to the community was that mariadb-k8s was an officially supported charm, not just a example / poc
[03:40] <wallyworld> good to know, ty
[03:41] <wallyworld> mostly, just in people's namespaces (eg ~juju) tends not to be "official" but there are excpetions so it's confusing
[03:41] <wallyworld> *stuff in
[03:42] <lucidone> Ahh, right cs:maria-k8s vs cs:~juju/maria-k8s
[03:42] <lucidone> I see "By juju" and "Stable" and jump to conclusions
[03:52] <lucidone> But thinking more on it; it's on jaas.ai/u/juju, and I got to the charm through google - not the charm store. So really, most of that confusion is probably on me
[05:25] <anastasiamac> wallyworld: PTAL https://github.com/juju/juju/pull/10995
[06:21] <anastasiamac> wallyworld: PTAL https://github.com/juju/juju/pull/10997 :)
[12:03] <achilleasa> manadart: small PR for fixing network-health-check https://github.com/juju/juju/pull/11000
[12:05] <manadart> achilleasa: Looking.
[16:02] <nammn_de1> manadart: up for a small review? https://github.com/juju/utils/pull/305
[16:03] <nammn_de1> reason: be able to use `generations and branches` as featureflags
[16:11] <manadart> nammn_de1: There shouldn't be 2 flags for that. I think someone has made an incomplete change.
[16:11] <manadart> nammn_de1: In any case, the patch looks OK, but let's get CI what it needs to run the checks and add a PR description.
[16:13] <nammn_de1> manadart: Right now, as you have pointed out, we 2.7 and develop, are different initially I wanted to make both to be the same. Then I was talking to rick_h and he suggested that we want to use branches and generations as featureflags .
[16:13] <nammn_de1> yea i will update them
[16:25] <nammn_de1> manadart: ci cannot run the checks, as grumpig is missing a lot of deps (we using a lot of processcalls). Locally they run just fine
[16:25] <nammn_de1> manadart: should i just go onto grumpig and install those?
[22:03] <babbageclunk> quick and easy review for someone? https://github.com/juju/names/pull/100
[23:04] <wallyworld> thumper: you ok to merge the 2.7 forward port? finished the review?
[23:54] <hpidcock> babbageclunk: LGTM