16:00:11 #startmeeting Octavia 16:00:11 Meeting started Wed Feb 25 16:00:11 2026 UTC and is due to finish in 60 minutes. The chair is gthiemonge. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:11 The meeting name has been set to 'octavia' 16:00:15 o/ 16:01:11 o/ 16:02:32 #topic Announcements 16:02:38 * Gazpacho release cycle 16:02:50 o/ 16:02:50 It's Feature Freeze week! 16:03:16 Woo! 16:03:18 (also final release for python-octaviaclient) 16:03:45 the timeline was very short to merge features 16:04:19 the next milestone is the RC1 (release candidate) in 2 weeks, until then we can continue to work on bugfixes 16:05:00 * CI Status 16:05:28 we fixed the CI (including stable branches)! 16:06:00 thanks to everyone who contributed! 16:06:28 No problem, we certainly could have done without it so close to feature freeze 16:07:56 that's all for my announcements, anything else folks? 16:08:08 None from me 16:08:13 Nothing on my end 16:08:30 #topic Brief progress reports / bugs needing review 16:09:09 reviews and CI fixing for me 16:09:28 I've been looking at the CR for the API performance improvements. After several hurdles I finally got my dev env up and running and tested it out. Seems good so I gave a +1 16:09:59 Next steps will be addressing comments on https://review.opendev.org/c/openstack/octavia/+/971408 16:10:29 And I also want to get my head around the multi AZ deployment CR - https://review.opendev.org/c/openstack/octavia/+/976100 16:10:39 great, i guess it can be merged at the begining of the next release cycle 16:11:36 Hopefully, the multi AZ one will be a big change so it would be nice to get it in early and give it time to settle (and throw up any potential bugs) 16:13:30 I'm not officially the PTL for the next cycle, but I started to list some topics for the PTG, multi AZ could be an important one 16:15:05 Does that mean we don't have a PTL? 16:15:10 Or how does that work 16:16:25 well, for gazpacho, I guess I'm like the acting PTL 16:16:42 for the next cycle, I should be PTL as I was the only candidate 16:16:57 o7 16:17:17 o7 16:17:25 I think I cannot lose the election if I'm the only candidate 16:17:35 :D 16:17:50 This would be the single party system :D 16:19:28 #topic Open Discussion 16:19:51 Merged openstack/octavia stable/2024.2: Fix database connection check https://review.opendev.org/c/openstack/octavia/+/975193 16:20:22 Sorry to keep pinging about this, but 16:20:25 #link https://review.opendev.org/c/openstack/octavia/+/976490 16:21:06 Keep pinging, it slipped off my radar last week :( 16:21:07 I'm trying to package up https://review.opendev.org/q/I34341e1aaad1524e3e0834309c5f6897f176af53 for older releases but I'll need to bundle this follow up with 16:21:08 ack, I put it on my todo list, I want to test potential corner cases 16:21:17 ty 16:21:40 oslo's behavior during startup and is a bit counterintuitive 16:22:19 as an aside it looks like sending a SIGHUP to octavia-wsgi doesn't work, at least when using mod_wsgi 16:23:02 you mean, to reload mutable config? 16:24:07 well yes. 16:24:14 ok 16:24:18 but also octavia-ovn-provider for example errors 16:24:40 because it tries to add cli options to oslo on init 16:24:46 and oslo.config errors 16:24:54 I gues sthat's an ovn-provider bug 16:27:45 hmm interesting 16:28:41 #link https://github.com/openstack/ovn-octavia-provider/blob/0f370ad761133c14d73917d5fdd392e684b4b512/ovn_octavia_provider/driver.py#L49 16:29:08 since as I understand, mod_wsgi reuses the interpreter but recreates the wsgi entrypoint 16:29:41 I remember that it was messy in the past, we had to fix issues simultaneously in octavia and the ovn-provider 16:29:47 ok 16:33:05 anything else for today folks? 16:33:19 Nothing from me 16:34:15 nope 16:34:39 ack 16:34:45 thank you folks! have a good one 16:34:48 #endmeeting