14:00:47 #startmeeting networking 14:00:48 Meeting started Tue Jan 17 14:00:47 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:48 The meeting name has been set to 'networking' 14:00:48 o/ 14:00:57 o/ 14:00:57 hello all 14:00:58 o/ 14:01:02 o/ 14:01:03 o/ 14:01:18 o/ 14:01:26 o/ 14:01:48 obondarev_, slaweq hi folks! 14:01:57 hi 14:02:01 I think we can start now 14:02:10 sorry for being late 14:02:15 np 14:02:23 #topic announcements 14:02:25 Antelope / 2023.1 schedule: https://releases.openstack.org/antelope/schedule.html 14:02:38 we are now in R-9 14:02:42 o/ 14:03:01 and there is a bunch of releases patches to be reviewed 14:03:04 #link https://review.opendev.org/q/project:openstack%252Freleases+status:open 14:03:23 we are releasing a new stable/xena version 14:03:43 apart from the Neutron repo (there are one pending patch), I think we are ok for the rest of them 14:03:54 please review them if there is something pending still under review 14:04:02 that should be released 14:04:33 I think these are relevant for us: https://review.opendev.org/q/project:openstack/releases+status:open+net 14:04:54 well, and the os-ken patch 14:05:04 and other networking repos I dont' see there 14:05:22 neutron-lib, networking-* 14:05:33 true 14:05:43 in any case, the list if short 14:05:50 is short* 14:06:12 something else to be commented in this topic? 14:06:33 let's for for the funny part 14:06:36 #topic bugs 14:06:48 lucasagomes' report this week 14:06:57 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031796.html 14:07:11 all the patches are triaged and assigned 14:07:15 except from 14:07:18 \o/ 14:07:19 #link https://bugs.launchpad.net/neutron/+bug/2002577 14:07:27 * mlavalle was toquick 14:07:28 but, IMO, slaweq's comment is correct 14:07:38 this is why I've marked it as invalid 14:07:50 slaweq saved the statistics :-) 14:07:56 right! 14:08:01 thanks slaweq \o/ 14:08:06 in any case, please check this one 14:08:22 :) 14:09:20 and the Fortune is touching this week to jlibosva, that is the bug deputy 14:09:27 o/ ack 14:09:32 and next week will be obondarev 14:09:38 ыгку 14:09:41 thank you folks 14:09:42 sure 14:10:05 next topic 14:10:10 topic #specs 14:10:18 (there is nothing related to n-lib nor os-ken) 14:10:29 #link https://review.opendev.org/c/openstack/neutron-specs/+/867979 14:10:39 I think it is ready, just need to rebase it 14:10:51 yeap 14:10:55 I'll do it today 14:11:25 (ok, there is a merge conflict, I'll check it later) 14:11:30 and the second one is 14:11:32 #link https://review.opendev.org/c/openstack/neutron-specs/+/868076 14:11:37 I can take a look at it and then review it 14:11:41 it had a +W 14:11:45 mlavalle, thanks 14:12:00 I rebased 868076 on top of master, that's all 14:12:07 if you can +W, that will help a lot 14:12:21 it failed zuul 14:12:35 and, again, thanks for your attention on reviewing the specs 14:12:57 mlavalle, yeah, we can check what is happening there later, but the spec is ready to be merged, IMO 14:13:21 I know, I didn't W+ when I reviewed it to let other team memebers to look at it 14:13:54 and we can jump to the next topic 14:14:00 #topic community goals 14:14:06 1) Consistent and Secure Default RBAC 14:14:12 slaweq, did you talk to gmann ? 14:14:21 no, I forgot about it 14:14:25 but I will do this week 14:14:25 about making sRBAC the default 14:14:38 perfect! and thanks for taking care of this feature 14:14:46 once you have this patch, ping us 14:14:49 before making it default, I will first try to run our ci jobs with secure rbac enabled 14:14:56 and then we can think about switching it 14:14:59 right, much better 14:15:32 +1 14:16:15 so ping us when you have any testing patch or any news 14:16:21 sure 14:16:29 next one is 14:16:31 2) Neutron client deprecation 14:16:41 lajoskatona, pushing patches to this topic 14:16:46 we have 14:16:49 #link https://review.opendev.org/c/openstack/python-neutronclient/+/869473 14:16:55 #link https://review.opendev.org/c/openstack/python-openstackclient/+/869447 14:17:05 I think those are the new patches from the las week 14:17:13 yes those are fro trunks I think 14:17:26 and all related to BGP 14:17:30 #link https://review.opendev.org/c/openstack/openstacksdk/+/869485 14:17:51 and the n-lib patch 14:17:53 #link https://review.opendev.org/c/openstack/neutron-lib/+/870582 14:18:04 my other "we can do it" patch is for BGP, with that I hope tomorrow I can push a final version for SDK 14:18:16 perfect 14:18:19 thanks ralonsoh for the links 14:18:26 btw, can you group them in one topic? 14:18:36 just to have a better filtered list 14:18:42 yes, I will use one topic for them 14:18:48 thanks a lot 14:19:17 ^^^ so folks don't hesitate to review those patches (and, if you can, to colaborate on this bug) 14:19:24 #link https://bugs.launchpad.net/neutron/+bug/1999774 14:19:36 before pushing a patch, talk to lajoskatona 14:19:43 to sync efforts 14:19:59 lajoskatona: if you need help, I can help 14:20:01 worst case we can create an etherpad or such to track it 14:20:10 that will be perfect, 14:20:11 mlavalle: thanks we can sync offline 14:20:19 lajoskatona: ok 14:20:19 if you can create it and link in the bug, that will help 14:20:59 (in a couple of releases will deprecate the whole n-client project, I hope, not only the CLI) 14:21:35 let's move then to the last topic 14:21:39 #topic on-demand 14:21:42 I have 2 topics 14:21:56 to have a "pinging list", suggested by elvira and slaweq 14:22:07 for this meeting, the CI meeting and the drivers meeting 14:22:24 a list of nicknames that the meeting chair will paste on the channel 14:22:38 to ping you,if you want to "subscribe" to this service 14:22:56 that "ping" doesn't imply you must attend the meeting, is just a courtesy ping 14:23:24 I'll add a section in the Neutron meeting and the drivers meeting 14:23:40 good idea 14:23:41 and I'll send the link in a mail to anyone that wants this 14:24:10 and the second topic is 14:24:10 if You want to be on such list for ci meeting, please just let me know on irc 14:24:16 I will add You to the list 14:24:21 slaweq, perfect 14:24:28 I'll add the CI meeting link too 14:24:37 ++ 14:24:44 I'll send the mail in 5 mins 14:25:05 the second topic is 14:25:08 tox envlist: keep "py38" or move to "py3" 14:25:33 so many projects are moving the default tox envlist from py3x to py3 14:25:45 that doesn't enforce the python specific version 14:25:47 good idea elvira ++ 14:25:47 is this still related to the new tox version or independent? 14:25:55 independent 14:26:15 just something we had under discussing with haleyb 14:26:44 py3 will work as is in any deployment 14:26:51 regarless of the python version 14:27:15 will not work for the versions that we don't support like py3.6 14:27:28 right. it was initially seen as a tox4 bug, but once that was fixed i thought it was a good idea due to the 2023.1 runtimes 14:27:38 ykarel, yes but this is the default tox env list 14:27:49 you can always enforce the tox test 14:27:55 -epy38 for example 14:28:01 for example, this nova change https://review.opendev.org/c/openstack/nova/+/861111 references the CT guide in the commit message 14:28:36 ralonsoh: but that doesn't work if you don't have python3.8, like on 22.04/jammy 14:28:46 yeap, but if we don't specify any env with -e, it runs all in envlist in tox.ini 14:28:57 and that will not work on distros with py3.6 as default 14:29:17 if we use py3 in envlist 14:29:47 so that's the point: 1) enforce the version and make it fail by default in some distros 14:29:48 ykarel but do we still support any distros with py3.6 as default? 14:29:51 do you want to support outdated distros or current ones, would be the question 14:30:15 we have a list of supported versions 14:30:19 this is just the default list 14:30:30 slaweq, no that's not supported but i think we don't restrict distros used for development 14:30:31 you can always enforce the version you want to run 14:31:03 according to https://github.com/openstack/neutron/blob/master/setup.cfg#L18 we are currently supporting only py3.8 and newer 14:31:06 not py3.6 14:31:26 yes and till now we had py38 and in tox.ini matching that 14:31:28 and I think it's the same for other deliverables which we have 14:31:45 https://governance.openstack.org/tc/reference/runtimes/2023.1.html says 3.8 and 3.10 only 14:33:08 i am ok with adding py3 in tox.ini, just wanted to raise as it will not work on some distros 14:33:21 the question is really just do we want to pick a specific python version if someone just runs 'tox' with no args. i think we should just use whatever the default on the system is since it might fail otherwise 14:33:55 haleyb I agree 14:33:56 ykarel: which distros will not work? 14:33:57 and those older distros can always pass the required version with -e 14:34:03 good point, that is important also to keep it work for the general user/developer 14:34:04 haleyb, centos 8 14:34:15 for ex 14:34:40 but for sure -epyxy can work always 14:35:50 ok, I don't want to make this discussion longer 14:36:12 I think most of us agree with having py3, not py3x by default 14:36:21 +1, agree 14:36:23 can you vote? py3 or py38 14:36:25 +1 14:36:26 +1 14:36:32 py3 14:36:34 py3 14:36:35 py3 14:36:37 py 14:36:38 py3 14:36:44 no matter what we do i'm sure the next tox4 bug will show we chose wrong :) 14:36:46 py3 14:37:13 perfect, thanks folks. So for any new tox related patch, please change it 14:37:26 and that's all I have 14:37:31 so you have something else?? 14:37:36 please remember about ci meeting, it starts in 23 minutes, on video https://meetpad.opendev.org/neutron-ci-meetings 14:37:40 ^^^^^^^^ 14:37:42 I just hope every project will have similar tactic (swich to py3), consistency++ 14:38:00 exactly 14:38:22 slaweq: ack 14:38:34 also just a quick congrats to all of you who worked on cleaning the lp backlog https://bugs.launchpad.net/neutron/?orderby=-importance&start=0 is down to 756 Open bugs 14:38:51 this spammed my launchpad inbox a bit, but for the good cause :) 14:38:56 exactly! thank you for adding the correct status 14:39:02 or closing it 14:39:18 we started this released with more than 1200 bugs 14:39:44 that's impressive cleaning indeed 14:39:48 (btw, I list of bugs I've closed due to innactivity: https://etherpad.opendev.org/p/neutron-manually-closed-bugs) 14:40:10 so keep going on this 14:40:58 thank you all and remember to comb your hair for the CI meeting on video in 20 mins 14:41:01 #endmeeting