16:00:11 <gthiemonge> #startmeeting Octavia
16:00:11 <opendevmeet> Meeting started Wed Feb 18 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 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:11 <opendevmeet> The meeting name has been set to 'octavia'
16:00:16 <gthiemonge> hi
16:01:54 <rcruise-redhat> o/
16:02:20 <gthiemonge> #topic Announcements
16:02:25 <gthiemonge> * Gazpacho release cycle
16:02:41 <gthiemonge> FYI this week is Final release for non-client libraries
16:02:48 <gthiemonge> octavia-lib for us
16:03:02 <raineszm> o/
16:03:27 <gthiemonge> AFAIK there's nothing waiting there (only rate limiting related patch but the feature is not ready)
16:03:54 <gthiemonge> next week is feature freeze and also final release for python-octaviaclient
16:04:17 <rcruise-redhat> Yeah I don't think there's any other features ready for this cycle
16:04:26 <gthiemonge> the neutronclient removal patch was merged last week, I think we're good to go with the client
16:05:07 <gthiemonge> regarding features I don't see anything that can be merged in one week (especially with one major reviewer missing)
16:06:08 <gthiemonge> I think stuff like API performance improvement can also wait, if we merge it at the begining of the next cycle we will have a lot of time to see how it behaves in the CI
16:06:45 <gthiemonge> anyway, if you have any concerns or any patches that need to be reviewed before end of next week, don't hesite
16:07:44 <gthiemonge> * PTL Election
16:08:18 <gthiemonge> we are in the nomination period for the PTL election, I sent my candicacy earlier this week
16:09:07 <gthiemonge> * CI stability
16:09:24 <gthiemonge> stable branches are still affected by the setuptools changes
16:09:37 <gthiemonge> https://review.opendev.org/c/openstack/octavia/+/976608
16:09:45 <gthiemonge> I updated this patch on 2025.2
16:10:39 <gthiemonge> it pins setuptools for most of the tox jobs (I think only pep8 really requires it) and it removes pkg_resources use in a test file, because pinning was not enough for the doc job
16:11:03 <gthiemonge> so please take a look, if it's ok, I'll approve it and backport it down to the other stable branches
16:12:13 <gthiemonge> that's all from me, any other announcements folks?
16:13:02 <rcruise-redhat> Nothing from me
16:14:33 <gthiemonge> #topic Brief progress reports / bugs needing review
16:15:48 <rcruise-redhat> I'm hoping to look at the VRRP peer security bug this week. It isn't a big impact but it would be nice to get it in this cycle or early next cycle
16:16:40 <gthiemonge> BTW release candidate 1 is targeted for March ~12
16:16:55 <gthiemonge> there's still time to fix bugs ;-)
16:18:21 <gthiemonge> on my side, I've been looking at different CI failures: setuptools, but also random failures that are probably caused by really busy CI at the end of the release cycle, some amphora VMs are really slow and sometimes it causes small issues in the tempest tests
16:20:27 <gthiemonge> and reviews of course
16:22:04 <gthiemonge> #topic Open Discussion
16:22:33 <raineszm> I've got a review and a semi related question
16:22:40 <raineszm> #link https://review.opendev.org/c/openstack/octavia/+/976490
16:23:03 <raineszm> ^ a follow up patch to properly remove failed providers from the list of enabled providers
16:23:26 <raineszm> and Q; how are reviews going to work without one of the cores
16:24:15 <rcruise-redhat> We're going to train an AI to pretend it's Michael :-)
16:24:22 <gthiemonge> ack, I see, we need to check the impact of set_override
16:24:37 <rcruise-redhat> raineszm: I'll take a look at that CR
16:24:50 <raineszm> rcruise-redhat: I'm sure the training is already in progress
16:24:57 <rcruise-redhat> :D
16:25:03 <raineszm> The need for the patch comes from how oslo works
16:25:04 <gthiemonge> A: any reviews are welcome even from non-cores of course
16:25:32 <gthiemonge> we can approve patches with only one CR+2, it's more problematic when I'm also the author of the patch :D
16:25:46 <gthiemonge> but right now we have no other solutions
16:25:58 <rcruise-redhat> gthiemonge: We'll just have to trust you
16:26:01 <raineszm> eh, it's reviewer you and submitter you. Two entirely diferrent people
16:26:12 <raineszm> Just put on a fake mustache and glasses when you submit
16:26:24 <rcruise-redhat> :-D
16:26:45 <gthiemonge> I'm using Claude Code for reviewing my own patches too, and TBH it detected some stupid things in my patch that no one noticed :D
16:28:11 <gthiemonge> I'm not the PTL of the next cycle yet (election is not finished), but if I am the PTL, we'll have a plan to help people to become core reviewers
16:28:43 <raineszm> Is any action required for the PTL election
16:29:24 <gthiemonge> if i'm the only candidate, nothing is needed
16:30:41 <gthiemonge> raineszm: rcruise-redhat: so guys, my advice is: don't hesitate to give CR-1 even if it's only for a question in patch, it gives more visibility to your questions and more visibility to your contributions to the other core-reviewers (me)
16:31:01 <rcruise-redhat> gthiemonge: Sounds good
16:31:19 <raineszm> gthiemonge: o7
16:31:27 <gthiemonge> as I said before, a good CR-1 is better than 10 CR+1
16:32:52 <gthiemonge> unfortunately stackalytics is broken :/
16:33:49 <gthiemonge> any other topics for this week?
16:33:58 <rcruise-redhat> None from me
16:34:03 <raineszm> all good here
16:34:15 <gthiemonge> thank you! have a good week!
16:34:17 <gthiemonge> #endmeeting