14:00:39 #startmeeting networking 14:00:39 Meeting started Tue Jun 25 14:00:39 2024 UTC and is due to finish in 60 minutes. The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:39 The meeting name has been set to 'networking' 14:00:41 ralonsoh I already +2 this patch 14:00:41 Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh 14:00:42 \o 14:00:46 o/ 14:00:47 slaweq, thanks! 14:00:49 hello 14:00:50 hi 14:00:55 o/ 14:00:59 o/ 14:01:17 o/ 14:01:42 o/ 14:01:56 #topic announcements 14:02:15 We are now in Dalmatian release week (R - 13) 14:02:17 #link https://releases.openstack.org/dalmatian/schedule.html 14:02:28 The Dalmatian-2 milestone will happen next month, on July 4th, 2024 14:02:35 At milestone-2, the release team will propose releases for any library that has not been otherwise released since milestone-1 14:03:06 So land any *-lib patches in the next week to make sure they land 14:03:29 o/ 14:03:41 deadline is end of next week? 14:03:44 or when exactly? 14:04:04 ahh, sorry, you said already 14:04:11 4th July 14:04:22 slaweq: yes, July did sneak up on us, it's next week 14:04:51 and like most in the US, i'll be offline 4th and 5th 14:05:00 \o/ 14:05:03 me too 14:05:08 do we have high prio items in n-lib to be merged quickly? 14:05:16 we need to +1 the release patches before this day then 14:05:28 lajoskatona, ^^ thanks! I would like to have it 14:06:12 #link https://review.opendev.org/q/project:openstack/neutron-lib 14:06:21 by the way do os-ken is in the same lib category as n-lib? Do we have to release that also next week? 14:06:28 late o/ 14:06:41 lajoskatona I believe os-ken is lib also 14:06:50 so it has the same deadline 14:07:09 lajoskatona: you must be asking about https://review.opendev.org/c/openstack/os-ken/+/922622 ? :) 14:07:11 so we need the os-ken patch for the dead loop 14:07:28 regarding neutron-lib I would maybe like to include https://review.opendev.org/c/openstack/neutron-lib/+/921649 if possible 14:07:33 ^^ is on my list right after meeting 14:07:40 haleyb: that one :-) 14:07:51 haleyb thx 14:08:18 slaweq: oh, i was pointing at the os-ken one, but will look at that once it passes functional :) 14:08:39 haha, sure 14:09:33 I will fix that failed tests just after this meeting 14:10:09 ack, i didn't know if it was just the gate, that job had been flaky i thought 14:10:33 I think it may be related to my changes there 14:11:13 Reminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers 14:11:31 i think there was one topic from mlavalle 14:11:57 there is one mine 14:12:07 ralonsoh: ack 14:12:20 the other one was regarding dns domain, https://review.opendev.org/c/openstack/neutron/+/920459 14:12:28 ++ 14:12:52 so there will be a meeting on Friday 14:13:29 mlavalle: thinking of 14:13:33 arg 14:13:57 haleyb: thanks! 14:14:01 mlavalle: thinking of D-2 milestone, was there any changes for ironic that we needed? 14:14:13 not that I know of 14:14:23 but I can check with them 14:14:32 and let you know later this week 14:15:01 mlavalle: ack, i left the note in our meeting wiki to remind myself but hadn't seen anything 14:15:20 I have no problem checking with them 14:15:58 any other announcements? 14:16:48 alright, next topic 14:16:54 #topic bugs 14:17:38 isabek was supposed to be deputy last week, but he pinged me late saying he could no longer to it 14:17:59 instead of moving everyone a week i just did it, but we are now down one deputy 14:18:37 so everyone make sure to see when your next week is, and if you cannot do it please ping me early, or swap 14:19:16 14 deputies is still a good number 14:19:35 it is. still, it is bad to see another one go 14:19:36 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/GTCE24CAUSUABSSCM6SDPGLQ6VPNQV4R/ 14:20:17 that was my report, it was mildly busy 14:20:31 and i had a couple of bugs to talk about 14:20:49 #link https://bugs.launchpad.net/neutron/+bug/2069689 14:21:31 this was regarding breakind n-d-r and vpnaas with wsgi changes - do we still need the neutron workaround now that patches have landed? 14:21:50 i.e. https://review.opendev.org/c/openstack/neutron/+/922185 14:22:26 we need new releases of these projects, to avoid people form downloading the lastest version with the error 14:23:07 but no, we should not need the neutron patch 14:23:17 this is only in master (that is dev only) 14:23:53 ralonsoh: ack, i just wanted to make sure i didn't miss anything, figured there would have been pings if still needed 14:24:13 we didn't release any Neutron version with this error 14:24:30 and next one will be used by the updated n-d-r and vpnaas 14:24:44 ^ we need to update the requirements once the next neutron is released 14:24:50 we had recent failures in dynamic-routing weekly jobs https://zuul.openstack.org/buildset/a21e500158db4abfa9f2c3cae8a73d3e 14:25:25 after the linked ndr patch merged, is there anything up to fix ^? 14:26:28 I have to ping the exabgp folks about the fix for py312 & bagpipe 14:26:44 ykarel: i didn't think so, is artem around? i'm bad at remembering nicks 14:27:01 gtema (Artem Goncharov) 14:27:14 slaweq: thanks 14:27:33 the problem is that n-d-r is retrieving a stable neutron version neutron-24.0.0 14:27:47 this neutron version has the wsgi module in the older place 14:28:03 so what we need is, asap, to release a neutron version and update the requirements 14:28:11 yes usually we releae a rc for these issues 14:28:19 release ---^ 14:28:20 or make these projects robust enough to import from 2 places 14:28:39 right, with a try/except 14:28:52 +1 14:28:58 I prefer, for now, the try/except option 14:29:02 with a comment to remove it 14:29:08 I think better is to release neutron 14:29:31 this try/except is necessary only temporary and would need to be dropped later - too much additional work 14:29:50 gtema, additional work? one patch? 14:30:08 that's ok but with the release you also need to update the requirements of the projects 14:31:06 under additional work I mean one patch introducing try/except and second dropping if afterwards (keeping it for long time is not cool) 14:31:33 haleyb, I'll propose them tomorrow morning and add all of you as reviewers 14:31:38 I think we can continue 14:31:42 I can push the try except if everybody agrees, but I can live with old school neutron rc release also 14:32:58 ralonsoh: ack, thanks 14:33:11 the other bug i wanted to mention was 14:33:16 #link https://bugs.launchpad.net/neutron/+bug/2069718 14:33:43 i see stefan did drop a comment he was working on a patch 14:33:51 I will comment on the LP bug 14:33:57 why northd is stopped? 14:34:13 this is a required service, if we stop it, how OVN is intended to work? 14:34:28 ralonsoh: thanks. i think to reproduce they stopped it, but in prodoction it's maybe just slow because it has a lot to process? 14:34:28 this is like in ML2/OVS stopping the OVS agent 14:34:47 haleyb that is also my understanding 14:35:21 stopping it kind of simulate of the slow down which they experience in the production 14:35:27 i.e. the NB DB was updated and live migration proceeded, but failed 14:35:41 but this is an scale problem 14:36:01 not a Neutron problem itself, they would probably need to improve the HW of the controllers 14:36:20 ralonsoh: right, i guess i saw the question as "is there another way for neutron to do this, like waiting for SB to update?" 14:36:45 the answer can be No, but wanted to see what others thought 14:36:54 maybe with Ihar's improvements with multiple port binding 14:37:02 (I don't have the patch here) 14:37:08 but should't neutron somehow restore VM's connectivity after live-migration at some point? 14:37:12 but this is not in Zed, for sure, but in newer versions 14:37:35 IIUC reproduce steps, in such case after migration is done connectivity is permanently broken 14:37:44 or maybe I am missing something there 14:38:16 that's the point: you can have a slow northd and regain connectivity 4-20 secs later (as state in the first line) 14:38:44 ahh, ok 14:38:55 you can detect the completion of live migration - nova tells us - requested-chassis field is updated back to single value 14:39:09 from the reproduction steps (step 4 in particular) I understood something different 14:39:19 ihrachys, but in newer versions, not zed 14:40:04 slaweq: i focused on step 4 as well 14:40:55 please drop any comments in the bug, and we can wait for any patch to see if it's worth taking 14:40:55 ihrachys, no, my bad: https://review.opendev.org/c/openstack/neutron/+/828455 this is in Zed too 14:41:31 nbctl commands have --wait=hv - these are supposed to wait for ovn-controller to get the memo 14:42:12 (I will admit I haven't given the LP much thought, so just spitting random ideas - will check later with more attention) 14:42:59 ihrachys: thanks 14:43:23 i had no other bugs, but maybe someone else has one to discuss? 14:44:06 ok, moving on 14:44:09 #topic specs 14:44:15 #link https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open 14:45:03 just one and it has -1 so waiting on an update 14:45:33 #topic community-goals 14:45:49 slaweq: any update on S-RBAC? 14:45:54 no updates about S-RBAC from me still 14:45:56 sorry 14:46:10 I need to get into this finally but still haven't got time yet 14:46:21 np 14:46:29 #topic on-demand 14:46:43 any other topics to discuss? 14:46:54 quick one: can we add "eventlet-deprecation" to community goals? 14:47:14 to weekly share the open specs, patches and strategies 14:47:42 for now, there are two open specs, one in the TC and the other one for oslo.services 14:47:42 ralonsoh: yes, that's a good idea, i can add it for next week 14:47:49 perfect, thanks, that's all 14:47:52 can I get someone to look at https://review.opendev.org/c/openstack/neutron/+/918151? 14:48:12 ralonsoh: and regarding your patches, do you need any reviews? 14:48:22 yes, if you don't mind 14:48:30 and the n-lib one I have open 14:48:40 mlavalle, ack, on my pile for tomorrow morning 14:48:51 ralonsoh: thanks 14:48:53 do they share a topic? or i'll just look in review emails 14:49:27 for now I'm opening bugs, for example to add new services running with wsgi 14:49:39 the ovn implementation with wsgi is related to the deprecation 14:49:45 eventlet deprecation 14:49:58 https://review.opendev.org/q/topic:%22bug/2069581%22 14:50:00 and 14:50:14 https://review.opendev.org/q/topic:%22bug/1912359%22 14:50:16 that's all 14:50:25 ack, thanks will look later 14:50:49 CI meeting is in 10 minutes, in-person ykarel ? 14:51:05 yeap video today 14:51:08 +1 14:51:14 see You there 14:51:43 ack, i might have to miss as someone is here to fix something in a few minutes 14:52:00 thanks for attending, ping if you need any reviews 14:52:04 #endmeeting