14:01:27 #startmeeting networking 14:01:27 Meeting started Tue Jul 18 14:01:27 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:27 The meeting name has been set to 'networking' 14:01:27 o/ 14:01:29 hello 14:01:32 o/ 14:01:39 o/ 14:01:39 hi 14:02:33 let's start 14:02:40 #topic announcements 14:02:51 as usual, the schedule of this release 14:02:54 #link https://releases.openstack.org/bobcat/schedule.html 14:03:00 o/ 14:03:17 next big event is at the end of August, the milestone 3 14:03:45 and of course, the openinfra videos 14:03:47 #link https://openinfra.dev/live/#all-episodes 14:04:02 a couple of personal heads-up 14:04:27 next week I'll be in PTO, so do you think we can skip next week meeting? 14:04:34 or someone else will chair it? 14:04:41 up to you, please vote 14:04:42 for me we can skip it 14:04:47 same 14:04:52 can skip 14:04:54 * mlavalle will lurk. having an internal company meeting 14:04:57 +1 skip 14:05:25 ok, thanks! I'll send a mail 14:06:14 and the second one is that I'll not propose my candidacy for the next cycle, because of personal reasons. During the next cycle I won't be 100% active and this is why I need to step down 14:06:26 of course I'll continue working in Neutron as now 14:06:34 but I'll need to take some weeks of PTO 14:06:57 anything else? 14:07:32 ok, let's go then 14:07:43 Thanks ralonsoh for all your efforts as PTL in last few cycles \o/ 14:07:44 #topic bugs 14:07:50 ykarel, thanks! 14:08:13 last week mlavalle was de deputy 14:08:16 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034428.html 14:08:22 we have some bugs to discuss 14:08:32 #link https://bugs.launchpad.net/neutron/+bug/2027605 14:08:39 I have assigned this one to myself 14:08:59 actually I'm working with averdaguer on this one (that is not easy) 14:09:10 it involves live migration + OVN + trunk 14:09:14 the full pack 14:09:24 next one 14:09:27 #link https://bugs.launchpad.net/neutron/+bug/2027742 14:09:35 this is a RFE that will be presented next Friday 14:09:53 (last Friday we didn't have qorum so I skipped the drivers meeting) 14:10:06 I think racosta will take this LP bug ^^ 14:10:16 we'll check it next Friday 14:10:24 and the last one 14:10:31 #link https://bugs.launchpad.net/neutron/+bug/2026757 14:10:38 ykarel, do you have an update on this one? 14:11:15 --> https://bugs.launchpad.net/neutron/+bug/2026757/comments/2 14:11:25 ralonsoh, just i tested with source install of dnsmasq and it didn't segfault 14:11:37 version 2.87 14:11:57 so it seems to be a problem with the version distributed in Lunar, right? 14:12:23 version in jammy is 2.86 and that has known issue 14:12:31 ah Jammy, not Lunar 14:13:10 should we keep the bug in Neutron (there is a dnsmasq{Ubuntu) ) one 14:13:24 actually we should maybe do a version check... 14:14:01 a sanity check, if the version deployed is 2.86 we can always write a warning message pointing to this LP bug 14:14:41 fix is in 2.87 but that's not included in jammy, lunar has 2.89 but it failed when installed in jammy(but that could be due to packaging issues when used in different OS), could be confirmed with source install 14:15:13 ykarel, do you have a reference to the dnsmasq error? for documentation purposes 14:15:15 but yes sanity check would be good, also need to check why we not seen this in our ovs jobs 14:15:30 maybe because we don't use IPXE 14:15:44 ralonsoh, it's segfault in bug descripition 14:15:56 like dnsmasq[81586]: segfault at 7c28 ip 00007f6e8313147e sp 00007fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] 14:16:16 yes but I mean if there is a reference to a dnsmasq bug, describing the error and the fix 14:16:34 https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q3/016562.html 14:16:43 its linked in bug description too 14:16:43 ooook, perfect! 14:16:52 right, I missed that, thanks! 14:17:09 (at the end of the description, right) 14:17:20 will you propose this sanity check? 14:17:28 I can do it if you don't have time 14:17:35 sure i can do that 14:17:41 perfect! thanks again 14:17:55 and that's all! 14:18:00 do you have any other bug? 14:18:32 ah, I almost forget (same as last week) 14:18:59 this week ralonsoh is the deputy, next week will be rubasov (we swapped positions) 14:19:16 so let's jump to the next topic 14:19:21 #topic community_goals 14:19:35 1) Consistent and Secure Default RBAC 14:19:46 #link https://bugs.launchpad.net/neutron/+bug/2026182 14:19:50 nothing new on this topic this week from me 14:19:59 slaweq, working 24h per day on this 14:20:14 he will have everything ready and tested on Friday, for sure 14:20:24 hehehe 14:20:36 I need to address comments in the patch https://review.opendev.org/c/openstack/neutron/+/887942 14:21:07 ah yes, this is for the n-lib master CI issue 14:21:18 and then hopefully we can make new neutron-lib release which will unblock main patch https://review.opendev.org/c/openstack/neutron/+/886724 14:21:30 but in the meantime reviews of the https://review.opendev.org/c/openstack/neutron/+/886724 are welcome :) 14:21:50 it's pretty big patch but it changes mostly unit tests modules 14:22:03 for sure! thanks for this patch 14:22:11 and once you have the n-lib one, ping us 14:22:22 and then we'll release a new n-lib version ASAP 14:22:28 generally I would like as many people as possible to check neutron/conf/policies modules and see if what I set for SERVICE role makes sense and maybe if I forgot about something more 14:22:47 that's all from me 14:23:05 qq: could be useful to have a list of calls that are handled by the service role? 14:23:14 or just a grep in the code is enough? 14:23:48 I'm affraid that such list may be quickly outdated :) 14:23:55 that's right... 14:24:00 this is an ongoing feature 14:24:36 ok, I have another idea but let me do a POC first 14:24:47 something like an API that provides this info 14:24:56 but this is just an idea now 14:25:20 I was rather thinkinig about some way to generate doc page from the source code automatically 14:25:37 to document our defaults 14:25:43 that's another good solution, yes. There should be a way to do this 14:25:57 if someone will override defaults - that's up to him/her :) 14:26:05 of course 14:26:11 I will add it to my todo list, but as next step 14:26:18 for sure, and thanks a lot! 14:26:19 after we will merge this service role patch 14:26:26 and after this will be working fine :) 14:26:52 the next item is 14:26:54 2) Neutron client deprecation 14:27:08 because Lajos is not here, I'll skip this update to the next week 14:27:23 but please, in the agenda https://wiki.openstack.org/wiki/Network/Meetings there is a list of patches to review 14:27:49 and that's all I have 14:27:54 #topic on_demand 14:28:01 anything else you want to share? 14:28:21 nothing from me 14:28:38 nope 14:29:00 nope 14:29:07 IMPORTANT: in 30 mins, in this channel, we'll have the CI meeting. It is important to attend and to collaborate. Thanks! 14:29:16 thank you folks, see you in 30 mins 14:29:16 ACK 14:29:27 #endmeeting