15:05:28 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:05:28 <opendevmeet> Meeting started Tue Oct 14 15:05:28 2025 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:05:28 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:05:28 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:05:33 <noonedeadpunk> #topic rollcall
15:05:35 <noonedeadpunk> o/
15:05:38 <noonedeadpunk> sorry for being late
15:05:40 <NeilHanlon> o/
15:05:40 <DavidGomez> o/
15:05:57 <NeilHanlon> also running a bit late and have to run soon 😅
15:06:27 <noonedeadpunk> courtesy ping jrosser
15:07:02 <jrosser> o/ hello
15:07:08 <noonedeadpunk> #topic ofccie hours
15:07:29 <noonedeadpunk> DavidGomez: NeilHanlon do you have any news on Ceph front?
15:08:23 <damiandabrowski> hi!
15:10:01 <DavidGomez> Started some PRs related to infra to build Ceph for Rocky SIG/Storage, few tickets opened too. I have some PRs to make related to release packages next I'll try and get that done this week. After that is once infra is in place is actual builds and testing
15:11:49 <noonedeadpunk> oh, sweet
15:11:54 <noonedeadpunk> great news, thanks!
15:12:38 <noonedeadpunk> We need to pick up a time slot for PTG
15:12:43 <noonedeadpunk> Which will be in 2 weeks
15:13:00 <noonedeadpunk> I don't think we have a lot of topic to discuss, so would suggest smth like 2h tops
15:13:18 <noonedeadpunk> (our etherpad is literally empty so far)
15:13:20 <noonedeadpunk> #link https://etherpad.opendev.org/p/oct2025-ptg-os-ansible
15:16:32 <noonedeadpunk> I'd suggest smth like Tuesday 15 - 17 UTC, but I see it's conflicting with the TC slot :(
15:17:11 <noonedeadpunk> we can do 14 - 16, but that is kinda too early for EST timezone...
15:17:59 <noonedeadpunk> or well, it's early only for PST?
15:18:22 <damiandabrowski> I'm starting vacation on 28th, so most likely I'll miss PTG :/
15:19:23 <noonedeadpunk> Yes, jsut in case we're talking about Oct 27 - 31
15:20:20 <noonedeadpunk> Hm, maybe we can do it on 27th?
15:20:25 <damiandabrowski> yeah yeah, so only Monday works for me. But I don't want to be a person who forces everyone to have a PTG on Monday only because of my vacation :D
15:20:53 <noonedeadpunk> schedule is kinda really empty on Monday: https://ptg.opendev.org/ptg.html
15:21:35 <noonedeadpunk> jrosser: what about your plans?
15:21:48 <jrosser> oh let me look
15:25:01 <jrosser> monday is good, 27th
15:25:29 <noonedeadpunk> ok, nice, 15 - 17 UTC?
15:25:44 <damiandabrowski> perfect!
15:25:45 <jrosser> yes thats fine
15:25:56 <noonedeadpunk> NeilHanlon: any opinion an that ^ ?:)
15:26:02 <jrosser> tbh i am not sure at all how much we have to discuss
15:26:07 <damiandabrowski> +1
15:26:38 <jrosser> i am finding it very difficult to find time on actual OSA code for some time now
15:27:12 <noonedeadpunk> well. we can discuss on how and if we wanna move forward from where we are as well
15:27:21 <noonedeadpunk> with limited resources and limited review capacity
15:27:32 <jrosser> maybe we think of one big thing to all look at
15:27:36 <jrosser> perhaps proxysql or something
15:27:48 <noonedeadpunk> oh, yes, wanna do that for a while really know
15:28:02 <jrosser> so ideas like that would be great to discuss
15:28:06 <noonedeadpunk> we have a repo ready to accept code for years now
15:28:32 <noonedeadpunk> https://opendev.org/openstack/ansible-role-proxysql
15:28:52 <noonedeadpunk> I just failing year after year to put any reasonable effort to make it happen
15:29:13 <noonedeadpunk> we also are having ansible-core 2.19 which is more ansible-core 3.0 tbh
15:29:30 <mnasiadka> oh, ansible-core 2.19 is nice pain
15:29:55 <noonedeadpunk> I already found that our modules don't like it at all
15:30:14 <noonedeadpunk> mnasiadka: have you already started working on it?
15:30:30 <noonedeadpunk> As I think my huge concern is on how to catch all potentially problematic conditions
15:30:52 <noonedeadpunk> given that there's no type conversion or smth like that
15:31:11 <noonedeadpunk> so you can't do just `if list` like you could
15:32:06 <mnasiadka> noonedeadpunk: yeah, we did - https://review.opendev.org/c/openstack/kolla-ansible/+/960333
15:32:17 <noonedeadpunk> wow
15:32:19 <noonedeadpunk> ok
15:32:20 <noonedeadpunk> I see
15:33:17 <mnasiadka> Basically we need to support 2.19, because it’s how Kolla-Ansible release cadence is done - we bump one version each cycle (we test 2.18 and 2.19 in Flamingo in theory, but 2.19 is complicated). We don’t really backport Ansible version support.
15:33:23 <noonedeadpunk> mnasiadka: do you know if ansible-lint already catches that?
15:33:41 <mnasiadka> I don’t know, our ansible-lint ,,framework’’ needs a lot of work :)
15:33:43 <noonedeadpunk> we do around same fwiw
15:33:52 <mnasiadka> We use some old version with a lot of exceptions
15:34:10 <noonedeadpunk> because when I tried ansible-lint during 2.19 being in beta it was isntantly crashing with stack trace
15:34:23 <mnasiadka> Would probably make sense to make it better, but with 3-4 active cores it’s a bit hard :)
15:34:27 <noonedeadpunk> and I don't have time to check on that after release
15:34:54 <noonedeadpunk> we're exactly in the same boat here.
15:35:52 <noonedeadpunk> yeah, so catching all these conditions everywhere sounds indeed like a huge pita
15:36:39 <noonedeadpunk> oh, well. we actually support only 1 ansible-core version , not 2
15:36:57 <noonedeadpunk> anyway, that looks super fun indeed
15:37:11 <mnasiadka> Well, I think there’s a config knob you can use to make majority of these new things go away, but still that’s some work - and you need to fix it sooner or later
15:37:41 <noonedeadpunk> we are not having multi-repo, so it's a knob 20 times...
15:37:49 <noonedeadpunk> or well. a bot :)
15:38:19 <noonedeadpunk> I guess that is why I was asking about ansible-lint, because it used to have an auto-fix feature
15:38:21 <mnasiadka> Right, it’s easier for us - we only have two repos (kolla-ansible and ansible-collection-kolla)
15:38:30 <mnasiadka> And there’s Kayobe, but it’s another boat :)
15:44:43 <damiandabrowski> FYI, my PKI patches are ready for reviews
15:44:45 <damiandabrowski> #link https://review.opendev.org/q/topic:%22osa_hashi_vault%22+and+status:open
15:45:04 <noonedeadpunk> Oh, yes, sure, thanks for the update!
15:45:18 <damiandabrowski> i think there's only one active discussion left: https://review.opendev.org/c/openstack/ansible-role-pki/+/948881/comment/ee0404e1_b5ac6aae/
15:45:31 <noonedeadpunk> I'd say I'll try to review them... But the truth is that I'm having a plane to summit tomorrow morning
15:45:54 <damiandabrowski> on last meeting I promised to do something, but when I started working on it, it turned out to be quite problematic :/
15:46:01 <damiandabrowski> no worries
15:46:37 <damiandabrowski> btw. do you know why jobs are not triggered after recheck here?
15:46:38 <damiandabrowski> https://review.opendev.org/c/openstack/openstack-ansible/+/948889
15:49:49 <noonedeadpunk> um, no, not at first look
15:51:01 <opendevreview> Damian Dąbrowski proposed openstack/openstack-ansible master: Enable openbao jobs  https://review.opendev.org/c/openstack/openstack-ansible/+/948889
15:52:22 <damiandabrowski> ahh, one of the dependent changes was abandoned. That might be an issue
15:53:23 <noonedeadpunk> yeah, just wanted to say thay likely realted to dependent changes
15:56:16 <noonedeadpunk> there were also comments about trying to use smarter defaults for ther "backend" itself, but I had not time so far to think about what we can simplify
16:00:50 <noonedeadpunk> damiandabrowski: it's running now
16:01:08 <noonedeadpunk> I have also proposed releases, except 2024.1
16:01:33 <noonedeadpunk> along with unfreeze of roles: https://review.opendev.org/c/openstack/openstack-ansible/+/963970
16:01:48 <noonedeadpunk> this we need to merge before we merge anything else ^
16:02:22 <noonedeadpunk> #endmeeting