16:01:43 #startmeeting Octavia 16:01:43 Meeting started Wed Apr 30 16:01:43 2025 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:43 The meeting name has been set to 'octavia' 16:01:55 Hello everyone 16:01:59 o/ 16:02:14 #topic Announcements 16:03:13 I don't have a lot today I am still catching up 16:03:36 same for me 16:04:02 Right now the top issue is setuptools 80 has dropped and breaks the old pbr way of creating wsgi scripts. 16:04:35 I created patches for that a few years ago, but there was some controversy about when to make the cut over. 16:04:59 As one person said, procrastination has led us to the day.... lol 16:05:07 :-) 16:05:36 Anyway, we can talk more about that later in the meeting. Any other announcements? 16:05:43 nop 16:05:54 #topic Brief progress reports / bugs needing review 16:06:25 Mostly I have been working on the above issue, but also getting stable branch releases out. There is still once pending I will get finished today I think. 16:06:27 I'm working on downstream tasks and I had some days off... so no progress :/ 16:07:20 Yeah, I was out all of last week, so still catching up. 16:08:53 #topic CI Status 16:09:38 So the hot item in the CI is the wsgi script generation. The open patch works, but we now have a problem that 2025.1 is also picking up the new setuptools, so the grenade jobs are all broken as well. 16:10:24 I spent some time yesterday trying to figure out a good way to pin setuptools in 2025.1, but didn't come up with any good ideas. If anyone has a thought, let me know. 16:11:02 to pin it in octavia? or in requirements? 16:11:10 I don't want to backport this patch as it is a breaking change for packagers and deployers. The old wsgi script will not be there (same if they use 80)... 16:11:54 In Octavia. If I remember right, it gets installed independent of requirements.txt (it's not even listed there). 16:12:20 hmm ok 16:13:29 We have pinned it in tox.ini before, but that isn't going to help with grenade. 16:13:44 So, I need to keep researching this I think.... 16:14:13 To unlock master, we can just make the impacted jobs non-voting. (I think someone did that on the proposed patch last night) 16:15:33 ack 16:15:45 Any other CI issues of note? 16:16:04 We are talking about this patch BTW: 16:16:06 #link https://review.opendev.org/c/openstack/octavia/+/902812 16:16:29 indeed an old one 16:16:48 Yep, but still useful after all that time. lol 16:17:28 #topic Open Discussion 16:17:38 Alright, any other discussions this week? 16:17:55 someone asked about the status of the jobboard backend 16:18:03 I think we have a spec proposal open: 16:18:05 #link https://review.opendev.org/c/openstack/octavia/+/948193?usp=search 16:18:14 it's still marked as experimental in the doc 16:18:21 If we have time we should start looking at that. It came out of the PTG 16:18:42 ack 16:18:55 Ah, yeah. I guess at this point it's main stream deployment, so we should update that. 16:19:28 yeah operators gave a positive feedback on it during the caracal PTG https://etherpad.opendev.org/p/caracal-ptg-octavia 16:20:03 I know one deployment backpedaled on that, but it wasn't due to the jobboard stuff, it was a management/political mistake and they are adding it back in a future release. 16:20:40 Are you working on a patch for updating that? 16:20:44 and this was in the news this week: https://www.reddit.com/r/openstack/comments/1k9yn9w/new_release_octavia_amphora_v2_is_now_supported/ 16:20:50 yeah I can do it 16:21:04 Great, thank you. 16:21:22 Yeah, I saw the Atmosphere announcement. Good stuff. 16:25:54 Ok, if that is all we can wrap it up this week 16:26:48 Thanks everyone for attending! 16:26:49 #endmeeting