14:00:19 <ralonsoh> #startmeeting networking 14:00:19 <opendevmeet> Meeting started Tue Jan 24 14:00:19 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:19 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:19 <opendevmeet> The meeting name has been set to 'networking' 14:00:20 <mlavalle> o/ 14:00:24 <ralonsoh> hello all 14:00:25 <obondarev> hi 14:00:30 <haleyb> o/ 14:00:35 <frickler> \o 14:00:39 <lajoskatona> o/ 14:00:49 <ykarel> o/ 14:00:58 <slaweq> o/ 14:01:22 <ralonsoh> let's start 14:01:26 <ralonsoh> #topic announcements 14:01:32 <ralonsoh> #link https://releases.openstack.org/antelope/schedule.html 14:01:41 <ralonsoh> we are in R-8 14:01:55 <ralonsoh> three weeks before the A-3 milestone 14:02:02 <ralonsoh> that is the feature freeze! 14:02:21 <ralonsoh> along with the requirements and clients freeze 14:02:28 <ralonsoh> please be aware of this 14:02:57 <ralonsoh> Also please check the Openinfra presentations 14:02:59 <ralonsoh> #link https://openinfra.dev/live/#all-episodes 14:03:02 <ralonsoh> there is a new one 14:03:13 <ralonsoh> Distributing OpenStack Architecture with BGP and Kubernetes Integration 14:03:19 <ralonsoh> #link https://www.youtube.com/watch?v=r8WLM9TM6w4 14:03:29 <mlavalle> ++ 14:04:07 <ralonsoh> it could be a bit scary, but this presentation provides a lot of information 14:04:16 <lajoskatona> thanks the topic is really interesting and it is on my watch list 14:04:26 <ralonsoh> and a very good starting point to know aboyt BGP (and kubernetes) 14:05:07 <ralonsoh> let's move to the next topic then 14:05:11 <ralonsoh> #topic bugs 14:05:20 <ralonsoh> this is the report from jlibosva 14:05:27 <ralonsoh> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031868.html 14:05:35 <ralonsoh> most of the bugs are attended now 14:05:43 <elvira> hi, sorry for the delay o/ 14:05:51 <ralonsoh> hi! 14:05:59 <ralonsoh> but we have 2 of them still not assigned 14:06:08 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2003532 14:06:21 <ralonsoh> ^^ for this one I'm spawning an env to try to reproduce it 14:06:35 <ralonsoh> but I didn't have time to start with it 14:06:47 <ralonsoh> you are welcome to check it too 14:07:03 <ralonsoh> the second one 14:07:06 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2003359 14:07:14 <ralonsoh> it seems to be a problem with a race condition 14:07:27 <ralonsoh> if you create and delete routers too fast 14:08:03 <ralonsoh> there is also a reproducer, forcing a wait sleep during the GW port creation 14:08:16 <ralonsoh> can anyone check this one? 14:08:51 <lajoskatona> I can check 14:08:57 <ralonsoh> lajoskatona, thanks a lot! 14:09:24 <ralonsoh> we also have a new RFE but we'll talk about this one later 14:09:39 <ralonsoh> this week obondarev is the deputy, next week will be isabek 14:09:44 <isabek> o/ 14:09:45 <obondarev> yep, on it 14:09:51 <ralonsoh> thanks folks 14:10:09 <ralonsoh> ok, I think we can move to the next topic 14:10:12 <ralonsoh> #topic specs 14:10:21 <ralonsoh> #link https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open 14:10:44 <ralonsoh> we have a new one: https://review.opendev.org/c/openstack/neutron-specs/+/870030 14:10:56 <ralonsoh> the RFE will be discussed this Friday 14:11:01 <ralonsoh> #link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers 14:11:38 <ralonsoh> about the second one https://bugs.launchpad.net/neutron/+bug/2003095 14:11:56 <ralonsoh> I'll ping the reporter to have it discussed during the drivers meeting 14:12:27 <ralonsoh> so, in advance, please attend to the drivers meeting next Friday 14:12:57 <ralonsoh> anything else on this topic? 14:13:36 <ralonsoh> ok, let's move to the next topic 14:13:36 <lajoskatona> Just a small one: the first patches are up for https://specs.openstack.org/openstack/neutron-specs/specs/2023.1/ovs-tx-steering.html so if you have time please check them (from rubasov :-) 14:14:39 <ralonsoh> I'm trying to find the links 14:15:12 <lajoskatona> I just found the api-def: https://review.opendev.org/c/openstack/neutron-lib/+/870080 14:15:54 <ralonsoh> ok, it will be better to use the launchpad bug topic 14:16:27 <ralonsoh> lajoskatona, ok thanks a lot, I'll add it to my review pile 14:17:04 <lajoskatona> thanks folks 14:17:21 <ralonsoh> let's move to the next topic 14:17:27 <ralonsoh> #topic community_goals 14:17:37 <ralonsoh> 1) Consistent and Secure Default RBAC 14:17:45 <ralonsoh> #link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/867518 14:18:01 <ralonsoh> slaweq, pushed a DNM patch using the new RBAC policies 14:18:34 <ralonsoh> did you have time to check what is failing there? 14:18:54 <slaweq> ralonsoh not yet 14:18:57 <slaweq> sorry 14:19:04 <ralonsoh> no no, no problem 14:19:16 <ralonsoh> btw, will we have the new RBAC enforced this release? 14:19:31 <ralonsoh> I mean, we'll we swap to this by default? 14:19:36 <slaweq> I'm not sure if it's not too late 14:19:42 <slaweq> I will sync with gmann about it 14:19:44 <ralonsoh> I think so too 14:19:47 <ralonsoh> thanks! 14:20:17 <lajoskatona> if yes I suppose it will be a good release with nervous people running around :-) 14:20:33 <ralonsoh> yeah, I don't know the status of other projects 14:20:52 <ralonsoh> but from Neutron point of view, we need to polish those failing tests 14:21:12 <ralonsoh> most probably missing permissions, users, etc 14:21:30 <slaweq> yes, it seems that mostly our internal RBAC isn't working fine with those new policies 14:21:51 <slaweq> I will open bugs for that today or tomorrow so we can work on them 14:22:06 <ralonsoh> that will be perfect 14:22:15 <ralonsoh> and thanks again 14:22:51 <ralonsoh> next one 14:22:53 <ralonsoh> 2) Neutron client deprecation 14:23:00 <ralonsoh> #link https://review.opendev.org/q/topic:bug%252F1999774 14:23:22 <lajoskatona> +1, thanks for the link 14:23:26 <ralonsoh> I hope we have the trunk commands migrated and released soon 14:23:36 <ralonsoh> we need another +2 in the SDK patch 14:23:54 <ralonsoh> and then we have the other sdk patch 14:23:56 <ralonsoh> #link https://review.opendev.org/c/openstack/openstacksdk/+/869485 14:23:56 <mlavalle> I can look at it today 14:24:02 <ralonsoh> thanks 14:24:14 <lajoskatona> mlavalle: you also have +2 rights for SDK< 14:24:16 <lajoskatona> ? 14:24:18 <ralonsoh> the SDK bgp patch is OK, IMO 14:24:25 <mlavalle> lajoskatona: ah no 14:24:32 <lajoskatona> :-( 14:24:52 <ralonsoh> we can ping stephenfin or Artem 14:24:55 <lajoskatona> I go and ask on sdk channel than to ask for review than 14:25:00 <ralonsoh> cool 14:25:01 <lajoskatona> ralonsoh: ack 14:25:20 <ralonsoh> and again, thanks for working on this 14:25:21 <slaweq> I have +2 in SDK repo, I will review it 14:25:22 <lajoskatona> frickler: if you can check the BGP patches that would be really helpful 14:25:37 <ralonsoh> ah, btw, just asking 14:25:48 <ralonsoh> do we want to push the patch removing all CLI from neutronclient? 14:26:07 <slaweq> ralonsoh I think it is time to do it finally 14:26:07 <ralonsoh> (do we really need that? or we can wait until we definetly remove the repo) 14:26:12 <ralonsoh> ok 14:26:14 <mlavalle> I think so 14:26:16 <ralonsoh> I'll do it this week 14:26:18 <slaweq> it was deprecated some time ago already 14:26:23 <slaweq> ralonsoh++ 14:26:24 <frickler> lajoskatona: I'll be away for the coming two weeks, will have to wait until after that 14:26:47 <mlavalle> lajoskatona: would you give me again the pointer to the etherpad? 14:26:52 <lajoskatona> frickler: ack, not urgent I think, it will be a long story anyway :-) 14:27:07 <lajoskatona> mlavalle: https://etherpad.opendev.org/p/python-neutronclient_deprecation 14:27:14 <mlavalle> Thanks! 14:27:23 <ralonsoh> I'll add this link to the bug 14:27:36 <lajoskatona> ralonsoh: good idea, should have done that 14:28:22 <ralonsoh> done 14:28:30 <lajoskatona> thanks 14:28:40 <ralonsoh> and I think we are done here 14:28:47 <ralonsoh> the last topic is 14:28:54 <ralonsoh> #topic on_demand 14:28:58 <ralonsoh> lajoskatona, please 14:29:02 <lajoskatona> thanks 14:29:38 <lajoskatona> I added one, gmann sent a mail regarding the maintainers on pypi: https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848.html 14:29:51 <lajoskatona> there is an etherpad: https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup 14:30:21 <lajoskatona> where I added our stadiums which suprisingly mostly have maintainers over openstack-ci 14:30:48 <lajoskatona> and the goal is today that QA (or TC) want to have only openstack-ci as maintainer for all openstack projects 14:31:20 <lajoskatona> I think this is a good goal, but as in the thread there are thngs which should be discussed 14:31:40 <opendevreview> Arnaud Morin proposed openstack/neutron master: Set DVR qr-xyz interfaces DOWN on backup node https://review.opendev.org/c/openstack/neutron/+/869741 14:32:08 <ralonsoh> but if we have pypi mantainers, that means we'll have someone that can release without any permission from OpenStack 14:32:26 <lajoskatona> if you check the etherpad some of the maintainers are now not active around openstack or Neutron, or even there is one really suspicious id (login.launchpad.net_179 ) 14:32:37 <ralonsoh> yeah 14:32:47 <lajoskatona> yes exactly, that happened with some horizon lib I think 14:33:07 <ralonsoh> checking those Neutron related repos, all of them are actively mantained by the Neutron community 14:33:32 <ralonsoh> I don't think we should allow external maintainers 14:34:01 <obondarev> +1 14:34:05 <lajoskatona> yes, and I hope that no deployment or build system depends in the outside world to have these rights for these people 14:34:25 <ralonsoh> for example, we all now otherwiseguy is the father of ovsdbapp. But if he wants to push something, he know how to push a patch and release (in openstack) a new version 14:34:42 <lajoskatona> exactly 14:35:05 <ralonsoh> so if you agree, I'll add the comment "Ok to remove additional maintainers" to all Neutron related repos 14:35:06 * otherwiseguy waves 14:35:07 <lajoskatona> and if there is some issue with the release the release team has the tools to fix it (I hope) 14:35:14 <ralonsoh> exactly 14:35:45 <lajoskatona> ok, that was it from me to have a quick discussion of this topic 14:35:47 <ralonsoh> sorry, just for the records, do you mind to vote on this? 14:36:00 <amotoki> I am fine with it. it is just because I created *-dashboard pypi projects per the project team guide 14:36:01 <lajoskatona> +1 to keep only openstack-ci as maintainer 14:36:16 <lajoskatona> amotoki: thanks 14:36:26 <obondarev> same here, +1 14:37:28 <ralonsoh> ok, thanks, I'll update the etherpad 14:37:48 <ralonsoh> and I have another topic 14:37:50 <ralonsoh> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031745.html 14:38:05 <ralonsoh> this is related to the in-person PTG 14:38:20 <ralonsoh> we know we have, at least this year, two virtual PTGs 14:38:53 <mlavalle> +1 14:38:54 <ralonsoh> the point here is what about the Vancouver event? 14:39:04 <ralonsoh> what should be the agenda? 14:39:23 <mlavalle> at the very least pizza and beer 14:39:27 <ralonsoh> you have proposed to have a lighweight agenda for this event 14:39:35 <slaweq> mlavalle++ 14:39:47 <ralonsoh> mlavalle, yeah but this is difficult to be justified 14:39:59 <lajoskatona> Shall we open an etherpad and collect topics? 14:40:02 <mlavalle> jokes aside, meeting in person is necessary after such a long time 14:40:02 <ralonsoh> I mean, if we don't have a good planned agenda, this year ( 14:40:03 <slaweq> and seriously, for sure some "feedback from operarors" or something like that 14:40:14 <ralonsoh> lajoskatona, yes, that could be a very good starting point 14:40:31 <ralonsoh> slaweq, yes, this is another good topic 14:40:39 <ralonsoh> even better is that is done in person 14:40:42 <ralonsoh> ok 14:40:48 <ralonsoh> I'll reply to the mail chain 14:40:55 <mlavalle> ralonsoh: do we have a deadline for an agenda? 14:41:00 <ralonsoh> and the first think I'll do is to create this etherpad 14:41:14 <ralonsoh> not really, I will ask TC folks 14:41:16 <lajoskatona> thanks 14:41:44 <ralonsoh> but just remember this Vancouver event is in june (13-15) 14:42:05 <mlavalle> so I'm pretty sure we can como up with an agenda that includes operators feedback, pizaa / beer and more topics 14:42:06 <lajoskatona> yeah, we started to beg for travel budget :-) 14:42:25 <ralonsoh> lajoskatona, exactly! (and this is a very accurate verb) 14:42:37 <mlavalle> let's start with the etherpad now 14:42:53 <ralonsoh> I'll do it tomorrow morning, I'll send a mail 14:43:06 <ralonsoh> and thanks for the feedback! 14:43:15 <lajoskatona> Sorry I have to run for my kid to school, o/ 14:43:18 <ralonsoh> sure 14:43:29 <ralonsoh> I think we don't have nothing else in the agenda 14:43:33 <ralonsoh> so thank you all for attending 14:43:40 <ralonsoh> and remember today we don't have the CI meeting 14:43:46 <ralonsoh> see you online! 14:43:49 <obondarev> o/ 14:43:52 <ralonsoh> #endmeeting