16:00:36 <gthiemonge> #startmeeting Octavia
16:00:36 <opendevmeet> Meeting started Wed May 15 16:00:36 2024 UTC and is due to finish in 60 minutes.  The chair is gthiemonge. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:36 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:37 <opendevmeet> The meeting name has been set to 'octavia'
16:00:40 <gthiemonge> o/
16:00:54 <johnsom> o/
16:01:27 <tweining> o/
16:02:04 <gthiemonge> #topic Announcements
16:02:11 <gthiemonge> * 2024.2 Dalmatian Release Schedule: Dalmatian-1
16:02:19 <gthiemonge> it's already Dalmatian-1
16:02:35 <johnsom> FYI: The OpenStack Summit Asia call for papers closes May 29th.
16:02:37 <johnsom> #link https://openinfrafoundation.formstack.com/forms/openinfra_asia_summit_2024
16:02:41 <gthiemonge> I can't remember if we defined some internal deadlines/milestones
16:03:03 <gthiemonge> Do you have anything for Dalmatian-1? patches, specs, ...?
16:03:20 <gthiemonge> johnsom: +1
16:03:59 <QG> o/
16:04:25 <johnsom> I was trying to think myself.
16:05:01 <johnsom> The SG spec is still open
16:05:07 <johnsom> As is resize
16:05:20 <johnsom> Though there are two of those, so confusing
16:05:20 <gthiemonge> I updated the SG spec this morning
16:05:48 <gthiemonge> mypy?
16:06:35 <johnsom> It's not a spec, last time I looked it was waiting on a requirements repo dependency
16:06:47 <gthiemonge> oh right
16:07:16 <gthiemonge> anywys, for spec, Dalmatian-1 is not a blocking deadline, just an internal milestone
16:07:33 <johnsom> Right, but it's great if we can land specs early in the cycle
16:07:35 <tweining> only a friendly reminder that we wanted to integrate the typing patches at the beginning of the cycle
16:08:13 <gthiemonge> +1
16:10:06 <gthiemonge> Any other announcements?
16:10:21 <gthiemonge> our last meeting was 3 weeks ago, I probably missed a few things
16:11:16 <tweining> I haven't even started with the rate limiting spec so far btw.
16:12:21 <tweining> re mypy/typing the requirements dep is merged now
16:13:18 <gthiemonge> ok
16:13:25 <gthiemonge> #topic CI Status
16:13:30 <gthiemonge> A few ongoing issues:
16:13:40 <gthiemonge> pylint was/is broken on master and 2024.1
16:13:51 <gthiemonge> the fix on master merged earlier today (thanks tkajinam!)
16:13:57 <gthiemonge> then I have a commit that pins pylint on 2024.1
16:14:01 <gthiemonge> https://review.opendev.org/c/openstack/octavia/+/919727
16:14:07 <gthiemonge> (already got W+1, should merge soon)
16:14:22 <gthiemonge> then 2023.1 gates are also broken because of grenade
16:14:33 <gthiemonge> IFAIK we have to disable grenade because zed is now unmaintained
16:14:37 <gthiemonge> https://review.opendev.org/c/openstack/octavia/+/919572
16:14:43 <johnsom> +1
16:15:53 <gthiemonge> that's all for the CI
16:15:59 <gthiemonge> #topic Brief progress reports / bugs needing review
16:16:11 <gthiemonge> as mentionned earlier, I have updated the spec for custom Security Groups on VIP ports
16:16:15 <gthiemonge> https://review.opendev.org/c/openstack/octavia/+/915114
16:16:46 <gthiemonge> I received a lot of feedback on this spec (thanks!) one important point was to not limit the feature to one SG per VIP, so I changed it a little bit, now the spec allows multiple SGs per VIP
16:17:12 <johnsom> I have been making progress on SRIOV for members. It now works in the normal create path. I have removed some old unneeded code with this change. I have also been testing nova/neutron failure cases to make sure we only roll back the member and not the LB, etc.
16:17:45 <johnsom> I also found a nasty bug I introduced late in the SRIOV for VIPs chain and have created a patch:
16:17:47 <gthiemonge> johnsom: nice!
16:17:59 <johnsom> #link https://review.opendev.org/c/openstack/octavia/+/919546
16:18:38 <johnsom> Reviews would be appreciated as this needs to be backported to caracal and is a MAJOR bug for people trying out the SRIOV for VIPs code.
16:19:00 <johnsom> It's bad enough I will probably propose a dot release of caracal once we land it
16:19:49 <tweining> approved
16:19:59 <gthiemonge> ack
16:20:09 <johnsom> Also of note, I fired up a Ubuntu 24.04 VM and ran tox. It hits two issues, the TaskFlow issue we have a patch for, and the requirements checks.
16:20:22 <gthiemonge> looking at the open backports for Caracal, I don't see any really urgent fixes
16:20:29 <johnsom> One of the requirements check jobs is easy to fix, the other I have no idea what is wrong with it.
16:21:56 <gthiemonge> does it use py312?
16:22:36 <gthiemonge> you mention taskflow, so I assume it does
16:22:42 <johnsom> Yes it does
16:24:12 <gthiemonge> speaking about taskflow, Octavia is a big user of taskflow, and I have a few open patches there, I think it's good to ask reviews here too
16:24:49 <gthiemonge> I have a fix for an issue that can happen when creating an A/S LB
16:24:54 <gthiemonge> https://review.opendev.org/c/openstack/taskflow/+/900746
16:24:56 <johnsom> Also of note, I tested out the Grafana dashboard with the latest versions of everything. It loads up fine, but I found HAProxy made a breaking change to the Prometheus "status" metrics. I have already figured out a fix, I just need to take the time to implement it.
16:25:39 <gthiemonge> (related to https://bugs.launchpad.net/octavia/+bug/2043360)
16:25:51 <johnsom> Ok, yeah, I have taskflow reviews on my todo list
16:26:00 <gthiemonge> and I've implemented an Etcd backedn for jobboard
16:26:10 <gthiemonge> https://review.opendev.org/c/openstack/taskflow/+/915492
16:26:14 <johnsom> We are going to need to land that py3.12 patch soon I think
16:26:18 <gthiemonge> don't know why it's V-1, I'll check that
16:26:35 <gthiemonge> johnsom: I'll review it
16:29:44 <gthiemonge> #topic Open Discussion
16:31:24 <johnsom> I think I covered all of my topics
16:31:37 <tweining> me too
16:32:05 <gthiemonge> cool!
16:32:16 <gthiemonge> then that's it for this week!
16:32:22 <gthiemonge> thank you guys!
16:32:29 <tweining> amen ;)
16:32:33 <gthiemonge> #endmeeting