14:00:27 #startmeeting networking 14:00:27 Meeting started Tue Jun 11 14:00:27 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:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:27 The meeting name has been set to 'networking' 14:00:33 Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh 14:00:34 \o 14:00:49 o/ 14:00:52 hello 14:00:55 o/ 14:00:59 o/ 14:01:17 o/ 14:01:23 o/ 14:02:10 looks like we have quorum 14:02:13 #topic announcements 14:02:24 We are now in Dalmatian release week (R - 16) 14:02:32 #link https://releases.openstack.org/dalmatian/schedule.html 14:02:53 o/ 14:02:55 o/ 14:03:57 we did do a neutron-lib release last week for some things, so it is being used in the gate, the 'bump' patch hasn't merged yet though 14:04:17 Reminder if you have a topic for the drivers meeting on Fridays, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers 14:05:56 and just a reminder that if you have a feature planned and haven't started work on it, please start working on it 14:06:22 i will go through the ptg notes this week as i had some items in there for this cycle 14:06:42 * slaweq needs to do the same 14:06:44 that was all i had 14:07:05 oh, and i see ralonsoh is back - welcome back! hope you had a good leave 14:07:13 thank you! 14:07:18 +1 14:07:32 +1 14:08:11 we can move onto bugs 14:08:13 #topic bugs 14:08:23 jlibosva was the deputy last week 14:08:32 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/W2TC6LKDC6FYKJK2MD22PUP3PGAT2HWM/ 14:09:11 there was one un-assigned bug 14:09:15 #link https://bugs.launchpad.net/neutron/+bug/2067851 14:09:23 Packets dropped in br-int bridge 14:10:20 large E-W burst shows packet drops, but drop counters don't show it 14:10:49 i think if we just added some notes on where else to look it would be helpful 14:10:57 (recommendation: not to use hybrid plug --> qvoxxx but native) 14:11:11 IMHO this is more likely to be asked on the ovs mailing list for example 14:11:56 slaweq: right, and hybrid plug as well, hadn't noticed that 14:12:07 i will add a quick note and mention the ovs list 14:12:29 I don't think hybrid plug is issue here as qvo is veth end which is in the br-int 14:12:47 so it probably wouldn't change if they would try non hybrid plug 14:13:06 but the linux bridge could be the one dropping the packages 14:13:18 oh, maybe 14:13:20 yeah 14:13:31 so that is one thing we can recommend them to check 14:13:41 if not then go to the ovs community IMO 14:13:51 it also didn't mention which ovs version, a 3.x release would be desired 14:15:47 all other bugs have assignees, i did have a question about one though 14:15:58 #link https://bugs.launchpad.net/neutron/+bug/2068761 14:16:28 mtomaska: this is a revert, but in the bug you mention 'selectin' 14:18:00 I think that the idea here is to do revert first and backport this revert to stable branches too 14:18:12 and later change it to use 'selectin' in master branch 14:18:13 ^^ agree (and the test this new option) 14:18:28 i don't know the back story of the original patch myself, but since i have a 'selectin' change up for review didn't want to miss this in my change 14:19:26 original patch was proposed long time ago when dansmith raised to us issues that neutron is making A LOT of the sql queries during e.g. tempest job run 14:19:27 but we can revert (including stable branches) and then apply your patch 14:19:31 i have a selectin discussion in on-demand 14:19:51 with ralonsoh we were trying to optimize it and the only thing we found was that query for tags 14:20:06 selectin is unrelated to revert; but yes, will have to pick up the change to not miss this instance of subquery 14:20:18 the only goal was that, to reduce the queries in the logs 14:20:20 but now it seems it caused performance regression in case when there is a lot of tags associated with port 14:20:30 slaweq: ack, just wanted to make sure ihrachys was happy as well since there was a -1 there 14:20:41 I am not happy with the commit message 14:21:13 1. it's malformed - there's a single line that spands hundreds of characters. 14:21:22 (which is minor but must be fixed) 14:22:16 2. it doesn't document what everyone claims about the number of logs being irrelevant to actual performance. which may be true - I don't question it - but then if that's the rationale, document it. it shouldn't be hard to make this claim in writing in commit message. 14:23:11 once these are handled, I will not -1 it. I will happily rely on others' knowledge about the number of logs not being a real issue. 14:23:30 ihrachys: ok, let's get the message fixed and better document the issue, not sure if mtomaska is around today 14:23:42 it's around and checking now 14:23:48 he is, seen him in slack 14:24:11 just to be clear - it wasn't about number of logs 14:24:41 "The initial reason for this change was to reduce amount of SELECT logs" 14:24:48 dansmith may have more details but IIRC he was trying to optimize i/o load made by ci jobs on the ci infra 14:24:56 quoting. so let's make the commit message correct, whatever the correct is 14:25:10 +1 14:25:24 and he came to the conclusion that neutron is far ahead of every other project with making sql queries 14:25:31 so we have tried to optimize that somehow 14:25:37 whatever patch wasn't from me was it? I was raising the flag about the query load yeah 14:26:09 but yeah, neutron was doing like an order of magnitude more select calls for a given run than other services 14:26:12 ihrachys I know that this is what current commit message says and I already explained to mtomaska that this is not correct 14:26:36 ok. then we shouldn't +2 patches with incorrect commit messages! :) 14:26:37 dansmith patch was from me :) 14:26:46 ack :) 14:27:25 ihrachys you're right, my bad. I just removed my vote 14:28:08 thanks. I think the next steps are clear - fix / clarify commit message. maybe if we still are not sure the revert is totally innocent, report a LP to follow up on it. 14:28:48 +1 14:29:22 are there any other bugs to discuss? 14:30:02 This week obondarev is the bug deputy, next week will be isabek 14:30:08 obondarev: is that good for you? 14:31:08 Jay Jahns proposed openstack/ovn-bgp-agent master: Announce lrp ip if advertisement method is subnet https://review.opendev.org/c/openstack/ovn-bgp-agent/+/921516 14:31:49 and since i have not seen isabek in a while, does anyone here work with him to ping him? 14:32:41 ok, i'll try and follow-up offline 14:33:12 #topic specs 14:33:27 #link https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open 14:33:46 haleyb: yes sure 14:33:49 slaweq: i think we can merge the pre-commit one, will look after meeting 14:33:57 obondarev: thanks! 14:34:16 thx 14:34:48 there is some discussion in the other 14:34:51 #link https://review.opendev.org/c/openstack/neutron-specs/+/920681 14:34:59 i have not reviewed yet 14:36:54 #topic community-goals 14:37:19 lajoskatona: i see the horizon change is green, hopefully you get some core reviews 14:37:35 I have to ping the horizon folks again to have attention 14:39:34 slaweq: i don't seem to have your current community goal in the wiki, will need to add it 14:39:48 thx 14:40:04 I still need to finish some internal tasks and then get back to the SRBAC stuff 14:40:10 still has service role, which is complete 14:40:18 ack 14:40:37 is there a consensus for the drop eventlet topic? 14:40:53 yes, but we need now to use service token while communicating with e.g. nova 14:41:10 lajoskatona consensus where? does neutron have any specific plans? 14:41:15 and test that (I need to sync with @gmann on that part at some point) 14:41:29 I mean the community as a whole (for this one: https://review.opendev.org/c/openstack/governance/+/902585 ) 14:42:16 the timeline i had (from the ptg) was 14:42:22 2025.2 for co-existence 14:42:29 2027.2 for migration 14:43:21 personally, i think it's a good plan in the governance doc 14:44:02 but neutron does not have an owner for any work at the moment 14:44:03 haleyb: ack, we go for asyncio? yes the last update is more concrete perhaps 14:44:19 did we check the tasks to fix that in neutron? 14:44:34 Merged openstack/neutron-specs master: Add pre-commit configuration https://review.opendev.org/c/openstack/neutron-specs/+/918306 14:44:37 for example, remove evenlet from agents, fix OVN with wsgi, etc 14:45:02 Jay Jahns proposed openstack/neutron-tempest-plugin master: Add check to pick up network's dns_domain if present https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/921772 14:45:05 haleyb, right, that needs an owner, first of all 14:45:49 ralonsoh: the OVN with wsgi is still an issue 14:46:07 the bug is still open 14:47:00 I'll ping Lucas to check the status 14:47:11 yes, and last i asked about it the work was non-trivial 14:49:28 so who's the owner? :) 14:49:57 I can take it and do my best 14:50:05 but for sure I'll need your help 14:50:30 thank you. I think we will need to read on it, I for one am not well versed in asyncio. 14:50:47 ralonsoh: thanks, and I will help where i can 14:51:44 let's move on 14:51:48 #topic on-demand 14:52:02 i had added two topics, but want to see if others have any 14:52:25 none from me 14:52:45 alright, my first was regarding 'selectin' load strategy 14:52:49 #link https://review.opendev.org/c/openstack/neutron/+/920933 14:53:14 once neutron-lib was released that started to pass 14:53:27 but it will need a rebase on the revert we mentioned earlier 14:53:54 and i now wonder if we should add a hacking check to not allow lazy='subquery' any longer 14:53:59 yes pls 14:54:23 haleyb, nice, btw so you observed that it also helped in memory usage with cover jobs? 14:54:23 good idea 14:54:42 the reason to merge that sooner than later was to get some cycles testing with it 14:55:07 ykarel: no, didn't seem to help memory consumption, but will try again with new neutron-lib 14:55:58 ohkk, CI should already have newer neutron-lib 14:56:48 ykarel: right, and i'll run some tests locally when a fresh VM, but 'coverage' tool itself seems to be the memory hog here 14:57:02 ack 14:57:27 ykarel: i will have to look at your changes regarding this, i did not forget 14:57:37 i.e. swap, etc 14:57:44 +1 14:58:20 my other topic was regarding a ptg goal - migrate from wsgi scripts to python module paths 14:58:53 there were two reviews posted right after ptg from stephenfin (thanks!) - i have since rebased and will do again if necessary, but need some reviews 14:59:01 https://review.opendev.org/c/openstack/neutron/+/916406 14:59:07 https://review.opendev.org/c/openstack/neutron/+/916407 14:59:47 so if anyone has some cycles, thanks in advance 15:00:12 and we are out of time 15:00:25 do we have/do we need devstack support for this? 15:00:26 ci meeting starts now, video today 15:01:04 lajoskatona: i think there was a patch for that, don't know if we need more for neutron, good question 15:01:10 lajoskatona: there should be related devstack patches, yes 15:01:22 https://review.opendev.org/q/topic:%22remove-wsgi_scripts%22 15:01:24 haleyb, frickler: thanks 15:01:41 thanks for coming everyone 15:01:46 #endmeeting