16:00:23 #startmeeting Octavia 16:00:23 Meeting started Wed Feb 7 16:00:23 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:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:23 The meeting name has been set to 'octavia' 16:00:26 hi 16:01:08 o/ 16:01:36 o/ 16:02:52 #topic Announcements 16:02:58 * EOL/Unmaintained releases 16:03:22 FYI we are transitioning Yoga to unmaintained, a final release of octavia for yoga will be released soon (10.1.1) 16:03:53 and Train and Ussuri releases are now EOL (End of Life) 16:04:33 * 2024.1 Caracal Release Schedule 16:05:00 a reminder, the final release for non-client libraries (octavia-lib) is in 2 weeks 16:05:26 and Caracal-3 milestone (Feature freeze, final release for client libs) is in 3 weeks! 16:06:37 anything to add guys? 16:07:34 Nope, just gasping for air given the short window we have 16:08:28 #topic CI Status 16:09:50 Now that Yoga is unmaintained for many projects, we need to remove the stable-yoga jobs from octaiva-tempest-plugin gates 16:10:00 tkajinam has proposed a change 16:10:05 https://review.opendev.org/c/openstack/octavia-tempest-plugin/+/907959 16:10:19 but it's currently blocked because of random failures in the CI 16:10:38 it seems that haproxy consumes too much memory during some tests and kills itself 16:10:46 we are working on a fix in 16:10:50 https://review.opendev.org/c/openstack/octavia-tempest-plugin/+/861743 16:12:12 #topic Brief progress reports / bugs needing review 16:12:29 Just a reminder we have 2 patches for important bugs/patches for the neutron auth settings 16:12:34 https://review.opendev.org/c/openstack/octavia/+/905794 16:12:37 https://review.opendev.org/c/openstack/octavia/+/907426 16:13:35 I have posted another patch in the SR-IOV chain enabling nftables on the VIP. 16:13:54 https://review.opendev.org/q/topic:%22add_tls_terminated_api_tests-patch16%22+-status:abandoned I've worked on THTTPS and HSTS tempest test patches and I think I fixed most if not all open issues 16:14:02 Hello guys sorry I´m late. I respond to you @johnsom about the resize. 16:14:03 This patch is semi-related and could use reviews for merge now: https://review.opendev.org/c/openstack/octavia/+/898863/1 16:14:13 It removes a bunch of dead code 16:14:42 I posted it in October and it hasn't had any reviews 16:16:53 pyjou Thank you, I think it was mostly about documentation and some guard rails on the resize flavor 16:18:30 I´m agree with you. I think we can add a check before resize that prevents resizing from one topology to another. 16:18:51 Yes, I think that is at least a good short term solution 16:19:24 Perfect, so I'll integrate it into my code 16:22:47 because I haven't brought that topic up for some time: 16:23:08 https://review.opendev.org/q/topic:%22mypy%22+repo:openstack/octavia please don't forget about the typing/mypy patches 16:23:40 https://review.opendev.org/q/topic:%22pyupgrade%22+repo:openstack/octavia ... and also the pyupgrade patches. I've split them into small parts so it's easier to review. 16:24:06 ack 16:25:45 #topic Open Discussion 16:27:37 o/ 16:27:54 do you want to talk about https://bugs.launchpad.net/octavia/+bug/2052455 ? 16:28:28 QG yep 16:29:30 my opinion on it: in case of multivip, the user has to explicitely pass all the subnets they want to plug (with vip_subnet_id or additional_vips[].subnet_id) 16:30:21 if a port is passed with vip_port_id, if it has only one subnet, the subnet is the vip_subnet, if it has multiple subnets and the user didn't specify them with the API, it's a validation error 16:30:35 like this 16:30:38 https://opendev.org/openstack/octavia/src/commit/bbb4713464eee61add6ce32427621e36fa4086e9/octavia/api/v2/controllers/load_balancer.py#L224-L226 16:31:10 IMHO the only thing that is missing is that the multivip feature is not validated when a port is passed to POST /loadbalancer 16:33:16 Totally agree with this 16:34:55 I can work on a fix 16:35:44 and I think the multivip feature is poorly (or not) documented, we need to improve it (with use cases, limitations, etc..) 16:39:22 I would agree with that 16:41:28 cool 16:41:42 QG: thanks for the bug report BTW! 16:41:58 +1 16:43:09 any other topics? 16:45:04 Nothing from me this week 16:46:00 ok 16:46:17 thanks for the discussion guys 16:46:19 bye 16:46:24 #endmeeting