14:02:51 #startmeeting networking 14:02:51 Meeting started Tue Feb 28 14:02:51 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:51 The meeting name has been set to 'networking' 14:03:01 ping bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, sahid, slawek, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu 14:03:02 o/ 14:03:06 \o 14:03:10 o/ 14:03:17 hi 14:03:22 o/ 14:03:56 o/ 14:04:24 hello all 14:04:33 we have a tight agenda, so let's begin 14:04:43 #topic announcements 14:04:57 First of all, the OpenStack schedule 14:04:59 #link https://releases.openstack.org/antelope/schedule.html 14:05:14 this is the RC-1 week 14:05:34 and this is why we have a bunch of release patches to review 14:05:36 #link https://paste.opendev.org/show/bVXlabBzaJ1OXCaMWNVo/ 14:05:43 I've reviewed all of them here 14:05:47 https://etherpad.opendev.org/p/ralonsoh_cases 14:06:18 For ovn-octavia-provider, there are a couple of patches that need to be merged in the next days 14:06:34 o/ 14:06:41 but these patches are attended 14:06:52 about vpnaas, I have more doubts 14:06:55 https://review.opendev.org/q/project:openstack/neutron-vpnaas+status:open 14:07:06 apart from the sqlalchemy patches 14:07:18 do you know what should be merged before the RC1? 14:07:46 good question to discuss 14:08:07 3 of them have a -W, I won't consider them 14:08:22 the OVN patch cannot be merged 2 days before the release 14:08:31 r1 is this week, so I would keep things back 14:08:32 and then we have older patches 14:09:21 so you propose to keep the current hash, right lajoskatona? 14:09:44 well, we should merge the sqlalchemy ones 14:09:46 if something is fix for critical issue we can always merge it next week, do backport to Antelope and have RC2 for that project 14:09:50 because those are legit bugs 14:09:54 https://review.opendev.org/c/openstack/neutron-vpnaas/+/875628 14:09:58 https://review.opendev.org/c/openstack/neutron-vpnaas/+/875626 14:10:18 ralonsoh, slaweq: yes we can backport anyway 14:10:29 slaweq, ok (in any case, please check ^^ these patches) 14:10:40 sure, I will 14:10:44 I'll update, if needed, the release patch hash 14:10:57 and about Neutron, I need to review the active patches 14:11:18 but we should focus now in bug fixes, not features 14:11:51 RC1 release patches are out now: https://review.opendev.org/q/project:openstack/releases+RC1 (at least some) 14:12:06 I've sent the link 14:12:08 #link https://paste.opendev.org/show/bVXlabBzaJ1OXCaMWNVo/ 14:12:15 this is the list of patches related to Neutron 14:12:24 ohh, yeah the same but filtered :-) 14:12:58 please don't hesitate to comment on them, I'll review them every day 14:13:06 ack 14:13:36 and a kindly reminder for the Bobcat etherpad: https://etherpad.opendev.org/p/neutron-bobcat-ptg 14:13:45 please add your topics for the next PTG 14:14:10 and check the openinfra videos: https://openinfra.dev/live/#all-episodes 14:14:21 two weeks ago we had a new one: VGPU Management by OpenStack Nova and Cyborg 14:14:27 #link https://www.youtube.com/watch?v=WUdkS9558p8 14:14:53 any other announcement? 14:15:44 let's move then 14:15:56 #topic bugs 14:16:12 last week report is from bcafarel 14:16:17 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032453.html 14:16:21 another busy week 14:16:32 some people are quite productive :) 14:16:40 the vpnaas bugs commented are already addressed 14:16:45 and thanks ralonsoh for picking up the 2 vpnaas bugs 14:16:54 yw 14:16:55 +1 14:17:08 the only one not assigned (or with a patch proposed) is 14:17:10 #link https://bugs.launchpad.net/neutron/+bug/2008062 14:17:17 Merged openstack/neutron stable/wallaby: Enable qos extension_driver in ovn_db_sync https://review.opendev.org/c/openstack/neutron/+/874145 14:18:01 but maybe we'll go back to this one during the CI meeting (in 40 mins) 14:18:30 and this week lajoskatona is the deputy, next week will be slaweq 14:18:40 ++ 14:18:43 ok 14:18:57 ack 14:19:24 there are no new patches in ryu/os-ken so we can skip this section 14:19:29 same for the specs 14:19:36 so let's move to the next topic 14:19:45 #topic community_goals 14:19:52 1) Consistent and Secure Default RBAC 14:20:12 here I would like to bring the topic proposed by lajoskatona 14:20:17 sRBAC patch backports to stable/zed 14:20:43 the community is asking us to backport the sRBAC functionality to Zed 14:20:53 slaweq, you have proposed most of the patches 14:21:05 but there are some of then that should be discussed 14:21:11 I proposed job for stable zed https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/874709 14:21:21 and this patch depends on few backports 14:21:34 perfect, the commit message is a good summary for this 14:21:38 if I'm not mistaken, that should be complete list of what's needed to make this job greep 14:21:41 Merged openstack/neutron-lib master: port-hint-ovs-tx-steering: api definition https://review.opendev.org/c/openstack/neutron-lib/+/873112 14:21:41 *green 14:21:43 yeah, I just brought it again as last week we discussed it and after more discussion with gmann it seems it is better to backport these 14:21:48 but lets see CI result first 14:22:08 perfect, so we all agree to backport this funcitonality to Zed? 14:22:23 IMO it's good to backport those fixes 14:22:38 (if CI is green and there are no conflicts with the current functionality) 14:22:49 +1, from me 14:22:57 officially this new S-RBAC policies aren't supported in Zed but still some folks may want to use them 14:23:05 like e.g. mnaser 14:23:24 I know, this is why I'm bringing this topic here 14:23:38 :) 14:23:48 my main concern is that we don't break anything in Zed 14:24:01 no, it won't break anything for sure 14:24:20 perfect, so +1 from me. I'll review the patches during the week 14:24:33 and thanks for taking care of this 14:24:55 the next topic is 14:24:57 2) Neutron client deprecation 14:25:06 lajoskatona, any comment on this? 14:25:26 openstacksdk 1.0.1 is out now 14:25:40 please check the etherpad: https://etherpad.opendev.org/p/python-neutronclient_deprecation 14:25:57 some ready to review patches: https://review.opendev.org/c/openstack/tap-as-a-service/+/867786 14:26:08 https://review.opendev.org/c/openstack/python-neutronclient/+/868321 14:26:31 And just to try it I jumped into designate and octavia, and the designate one was an easy: 14:26:37 https://review.opendev.org/c/openstack/designate/+/874991 14:26:59 but I have to discuss it with designate team 14:27:12 so some progress to start Bobcat slowly :-) 14:27:18 that's a fantastic job 14:27:32 btw, I'll add this etherpad to the meeting agenda 14:27:39 thanks 14:27:49 and please, ^^^ @all check these patches 14:27:53 good idea to make it more visibl 14:27:57 e----^ 14:29:02 done (including the active patches) 14:29:45 ok, we are going faster than I expected (that's good) 14:29:55 last section 14:30:00 #topic on_demand 14:30:05 I have a topic here 14:30:40 There is a list of lieutenants for different areas 14:30:44 #link https://docs.openstack.org/neutron/latest/contributor/policies/neutron-teams.html 14:31:09 some of them have only one single assignee (API, DB, control plane, client, docs, testing) 14:31:23 so the idea is to have at least two 14:31:39 +1 14:32:04 I can help with some of them for sure 14:32:20 of course we can't force anyone to be there, but the idea is to propose yourself 14:32:27 slaweq, you can suggest any area 14:32:44 of course, the more people we have, the better 14:32:56 You can add me to API and Testing 14:33:00 and, btw, you don't need to be core 14:33:02 and maybe Client if needed 14:33:16 slaweq, OK, I'll add you to these areas 14:33:23 Anton Kurbatov proposed openstack/neutron stable/zed: Prevent router_ha_interface port from being removed via API https://review.opendev.org/c/openstack/neutron/+/875737 14:33:25 ++ 14:33:26 thx 14:33:28 I can also add myself 14:33:41 lajoskatona, what areas? 14:34:14 btw, you can send your own patch hehehe 14:34:23 I anyway play with client code recently, but API can also be 14:34:27 sure 14:34:29 cool! 14:35:02 and this also for all the people in the ping list 14:35:10 Anton Kurbatov proposed openstack/neutron stable/yoga: Prevent router_ha_interface port from being removed via API https://review.opendev.org/c/openstack/neutron/+/875738 14:35:18 btw. I'm not sure if yamamoto wants still to be there :) 14:35:23 so please, you just need to push a patch and add your name in this list 14:35:23 he's not active recently 14:35:34 +1 for folks in ping list especially as it does not require core 14:35:35 I'll add a separate patch removing him 14:35:39 ok, I will propose myself there 14:35:40 and I'll add him to the review 14:36:29 and then there is the release liaison 14:36:52 Anton Kurbatov proposed openstack/neutron stable/xena: Prevent router_ha_interface port from being removed via API https://review.opendev.org/c/openstack/neutron/+/875739 14:36:56 I talked to amotoki (slawek, lajoskatona and mlavalle were in this mail too) 14:37:15 "Infra" means opendev-infra? 14:37:17 and he said that it will be better to step down from being the release liaison 14:37:30 frickler, yes and everything related to zuul and so 14:38:07 ralonsoh: ok, if you drop yamamoto there, you can add me instead, then 14:38:18 frickler, I'll push a patch for that, thanks! 14:38:43 * frickler can talk to self that way ;) 14:39:03 as long as you agree with yourself :) 14:39:18 oh, mostly I don't, sadly :D 14:39:32 so I'm going to propose a patch to drop amotoki from here 14:39:36 #link https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml#L86 14:39:37 it will be like in this move "me, Irena and myself" 14:39:38 I could not review release patches in time recently, so I think it is better to pass the release liaison role to someone 14:39:53 but instead of Irena there will be "Infra" :P 14:39:56 amotoki, thanks for all these years taking care of it 14:40:10 +100 14:40:12 ralonsoh: yw 14:40:24 ralonsoh and I can help with releases and be release liaison if it's ok for everyone 14:40:45 amotoki++ thx for great work in that role for many years 14:40:49 thanks amotoki :-) 14:41:34 slaweq, that will be perfect. I'm going to add me too (despite the PTL is always added by default to those patches) 14:41:40 we can have more than one person 14:42:22 the list of cross project liaisons are found here https://wiki.openstack.org/wiki/CrossProjectLiaisons 14:42:52 ralonsoh You don't need to be added as release liaison - PTL is treated in the same way in that case 14:42:57 uhh this is something I need to review too 14:43:12 slaweq, ok 14:43:42 ok, I'll check https://wiki.openstack.org/wiki/CrossProjectLiaisons too, but after this meeting 14:43:47 amotoki, thanks for this! 14:43:53 (too many lists!) 14:44:09 I am not sure the list is well maintained, but it explains what is expected 14:45:21 ok folks, this is all we have in the agenda 14:45:27 any other topic?? 14:45:59 Merged openstack/neutron master: Apply Ironic's server-ip-address as TFTP next-server https://review.opendev.org/c/openstack/neutron/+/875551 14:46:04 Merged openstack/neutron master: Remove two duplicated unit tests https://review.opendev.org/c/openstack/neutron/+/875571 14:46:07 ralonsoh there is also https://github.com/openstack/releases/blob/master/data/release_liaisons.yaml 14:46:09 Merged openstack/neutron master: Move register_common_config_options call to DietTestCase https://review.opendev.org/c/openstack/neutron/+/875552 14:46:27 which I think is used in the releases tools to add release liaisons to reviews 14:46:39 yes, this is the link I sent before, I think 14:46:48 ahh, ok 14:46:50 (well, mine was from opendev) 14:46:51 slaweq: yes, the release liaisons are maintained in that file and it is mentioend in the wiki page too 14:46:51 maybe I missed it 14:46:52 sorry 14:46:57 hehehe 14:47:24 don't forget that we have the CI meeting in 15 mins in this channel (today via IRC, if I'm not wrong) 14:47:28 see you all 14:47:31 o/ 14:47:34 #endmeeting