15:00:30 #startmeeting openstack_ansible_meeting 15:00:30 Meeting started Tue Aug 29 15:00:30 2023 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:30 The meeting name has been set to 'openstack_ansible_meeting' 15:00:34 #topic rollcall 15:00:36 o/ 15:00:37 hey ! 15:01:02 hi! 15:04:46 #topic office hours 15:05:00 I had quite short week, so obviously missed some things 15:05:26 heya folks 15:05:58 I guess for me most valuable part is to finally get 27.1.0, and I guess main thing we're missing for "safe" upgrades is https://review.opendev.org/c/openstack/keystone/+/892864 15:06:28 Senlin, that has been broken upgrade path is now fixed 15:07:18 For Adjutant - it's weird and I wasn't able to invest time there yet 15:07:41 as it's broken differently for lxc and metal, so I'm really not sure wtf is going there 15:10:28 keeping fingers crossed to merge #892864 ASAP 15:12:13 other then that, I've proposed to release ovs/ovn versions for stable branches 15:12:30 https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/892563 15:12:31 +1 from me on 892864 15:13:17 However, inside venv still old 2.17 buggy ovs will be installed due to constraints 15:14:02 https://review.opendev.org/c/openstack/requirements/+/892891 15:14:20 doesn't look like it's getting attention from requirements team though :( 15:18:16 Also, there's a patch to reduce amount of logs with journald 15:18:28 which would also allow for users to provide their rotation rules 15:18:40 https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/892151 15:18:55 This and releasing ovs version should help to solve disk_full for rocky 15:22:43 Then also would be nice if you could review patches for stable branches: https://review.opendev.org/q/parentproject:openstack/openstack-ansible+branch:%255Estable/.*+status:open+ 15:22:57 I was planning to issue role/service bumps for new releases 15:23:14 can do 15:25:07 I've also somehow missed to sign us up for PTG, as was sure I did that. THough I've sent a follow-up email and we should be in schedule 15:25:19 oh, awesome. i meant to ask about that 15:25:51 Though timeslots are not available yet, so too early to discuss date-time 15:26:02 I do see us on https://ptg2023.openinfra.dev/ now 15:28:23 Yes, and please register :) 15:28:31 done! :) 15:28:35 Not sure why - but that's needed 15:30:04 something something engagement metrics 15:31:16 but then moderators also write back attendance... 15:31:18 anyway 15:31:56 for ongoing development 15:32:53 and regarding quorum queues. 15:33:08 I see damiandabrowski has reviewd changes and reportedly tested them 15:33:27 There's also an ongoing improvement for that in oslo.messaging 15:33:29 #link https://review.opendev.org/q/topic:bug-2031497 15:33:34 yes, they look good from my perspective 15:34:04 Though I have really no idea if that oslo.messaging has any chance to be in constraints of 2023.2 15:34:31 I guess no, as we're beyond feature freeze for libraries and projects.... 15:34:58 As if they will - it would make sense to add couple of extra vars to control these new features 15:35:08 though this can be done in follow-ups... 15:37:36 yep 15:39:52 Once I will sort out current internal debts, I will try to look into Debian 12 support 15:40:02 as that is another thing that would be nice to land 15:44:59 that'd be great 15:45:29 on my side i'm tracking what's going on in centos and such for EL10. that's supposedly coming at some point, so, yeah 15:46:02 have you sorted out a way forward? 15:46:55 we have, yeah. we're more or less 'business as usual' just getting the sources from cloud instances for the most part. also working on the second generation of our build system https://github.com/peridotbuild/peridot/ 15:47:26 ok, great, nice to hear:) 15:58:17 #endmeeting