15:09:23 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:09:23 <opendevmeet> Meeting started Tue Jul 12 15:09:23 2022 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:09:23 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:09:23 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:09:28 <noonedeadpunk> #topic rollcall
15:09:44 <jrosser> o/ hello
15:09:48 <NeilHanlon> o/
15:09:50 <noonedeadpunk> sorry for being late again. Lost my alarm clock for starting meeting :(
15:09:58 <damiandabrowski> hi!
15:10:04 <mgariepy> hey
15:10:36 * noonedeadpunk just got notified that lsyncd available in centos 9s :D
15:11:00 <noonedeadpunk> #topic office hours
15:11:24 <noonedeadpunk> talking about centos, are there any news from Rocky ?:)
15:13:11 <NeilHanlon> We'll be releasing 9.0 this week :) I started a review for DIB to add in a build for 9, but i need to check in on it
15:13:48 <noonedeadpunk> nice!
15:14:12 <jrosser> hopefully it should be relatively painless as the centos-9 support is done
15:14:15 <noonedeadpunk> We just unblocked our gates after branching
15:14:42 <jrosser> i was just about to start going through taking out any centos/rocky-8 special cases on master
15:15:22 <noonedeadpunk> maybe we should wait then until r9 just in case?
15:15:36 <noonedeadpunk> but not sure
15:15:54 <noonedeadpunk> not sure in terms of value for such special cases
15:19:48 <jrosser> was just looking for PTG notes to see what we want to prioritise working on
15:19:49 <noonedeadpunk> I think main pain point for now are broken stable ranches because of rally
15:20:01 <noonedeadpunk> I think these would be internal ssl?
15:20:12 <noonedeadpunk> I'd love to have that for sure
15:21:26 <jrosser> that is sure a big job
15:21:43 <noonedeadpunk> and quite good profit
15:22:00 <noonedeadpunk> iirc we haven't merged bueprint yet
15:22:48 <noonedeadpunk> https://review.opendev.org/c/openstack/openstack-ansible-specs/+/822850
15:23:39 <noonedeadpunk> it looked pretty fair as well as poc. I have a bit vague memories of that topic, but it was super close
15:24:15 <jrosser> i think the basic idea is figured out with glance as an example
15:24:26 <jrosser> and the dual-mode haproxy setup
15:26:13 <noonedeadpunk> Btw regarding PTG
15:27:00 <noonedeadpunk> Until August 12th (basically a month) I need to signup team for it
15:27:09 <noonedeadpunk> As you might now it's in person even in US.
15:27:25 <noonedeadpunk> So I was wondering if anybody was thinking about going there
15:27:48 <mgariepy> what is the date ?
15:29:03 <mgariepy> October 17-20, 2022
15:29:33 <noonedeadpunk> Yup
15:29:54 <noonedeadpunk> Columbus, OH
15:33:41 <noonedeadpunk> As I was thinking of going there, but not sure how to handle that.
15:33:49 <NeilHanlon> don't go there, tis a silly place
15:33:53 <noonedeadpunk> that = tema registration
15:33:59 <noonedeadpunk> *team
15:34:09 <noonedeadpunk> NeilHanlon: oh, why?
15:34:48 <NeilHanlon> joking, mostly. it's about as dangerous as most American cities, which isn't saying much lol
15:35:53 <NeilHanlon> I would offer to drive/fly out there, not too far for me in Massachusetts, but the timing wouldn't line up unfortunately
15:37:28 <noonedeadpunk> ah, gotcha
15:38:06 <noonedeadpunk> I will try to think about how to make it in a mixed way actually. So everybody would be able to participate
15:39:10 <jrosser> i am really not having much desire to travel tbh
15:39:28 <noonedeadpunk> As eventually hearing talks during summit I think in-person PTG is good thing now
15:39:35 <mgariepy> i probably wouldn't go either.
15:39:53 <mgariepy> but i would do online :)
15:40:37 * noonedeadpunk wonder if other teams also prefer online
15:44:08 <noonedeadpunk> I think another good/big thing is support of tick/tock releases and upgrades through releases
15:44:30 <noonedeadpunk> Should be quite easy to implement but already I feel pain from circular dependencies
15:44:46 <noonedeadpunk> (that's what we discussed on previous PTG)
15:47:24 <jrosser> does that really end up with running N-2 upgrade jobs as well as N-1
15:47:47 * jrosser guesses it's more subtle than that
15:48:37 <jrosser> and maybe we have to keep one extra older branch alive
15:54:01 <opendevreview> Merged openstack/openstack-ansible-rabbitmq_server stable/wallaby: Use cloudsmith repo for rabbit and erlang  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/846122
15:55:53 <noonedeadpunk> regarding keeping older branches alive, I think it should be taken into account for release cadence anyway
15:56:50 <noonedeadpunk> but yes
15:57:04 <noonedeadpunk> my biggest fear is how subtle CI would be.
15:57:39 <noonedeadpunk> But we have quite good stats regarding upgrade jobs, and looking back to V - they're still passing if not erlang and rally...
15:57:59 <noonedeadpunk> more problematic would be to keep distro support
15:59:46 <noonedeadpunk> but again, given that upgrade path should be followed by services, they should not implement breaking changes in the meanwhile. But might be issues with upgrade releases
16:04:59 <noonedeadpunk> #endmeeting