14:00:12 <lajoskatona> #startmeeting networking
14:00:12 <opendevmeet> Meeting started Tue Nov 30 14:00:12 2021 UTC and is due to finish in 60 minutes.  The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:12 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:12 <opendevmeet> The meeting name has been set to 'networking'
14:00:16 <mlavalle> o/
14:00:19 <lajoskatona> Hi everybody!
14:00:21 <obondarev> hi
14:00:21 <lajoskatona> o/
14:00:26 <isabek> Hi
14:00:37 <frickler> o/
14:00:47 <rubasov> o/
14:00:51 <amotoki> o/
14:01:07 <ralonsoh> hi
14:01:13 <manub> hi
14:01:37 <lajoskatona> How fresh everybody is to join :-)
14:01:43 <lajoskatona> I think we can start
14:01:47 <lajoskatona> #topic Announcements
14:02:10 <lajoskatona> The usual reminder to check the Yoga cycle calendar: https://releases.openstack.org/yoga/schedule.html
14:02:25 <lajoskatona> It's week R-18: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025986.html
14:03:42 <lajoskatona> Last week we were really enthiasts and jumped to the topic of python runtime version, but for this week it seems it was too early
14:03:55 <lajoskatona> The mail thread: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025881.html
14:04:13 <lajoskatona> and a recent summary from gmann: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026024.html
14:04:19 <bcafarel> late o/
14:04:37 <lajoskatona> it seems that we keep py36 in Yoga
14:04:42 <lajoskatona> Hi bcafarel
14:06:01 <lajoskatona> Yesterday there was an edge vs. networking meeting/workshop :http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026062.html
14:06:17 <lajoskatona> I couldn't participate, I hope I can find the recording somewhere
14:06:29 <lajoskatona> was there anybody perhaps who participated?
14:07:26 <lajoskatona> anyway I have to check with ildikov how to progress with the topic we have from PTG to document edge networking deployment somewhere
14:09:15 <lajoskatona> this was the mail I sent out: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025811.html but actually I haven't seen answers on it, so I suppose we have to jump to the void with this topic :-)
14:09:55 <lajoskatona> Ok, I have no more news or announcements
14:10:25 <lajoskatona> #topic Bugs
14:10:36 <lajoskatona> ralonsoh was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026043.html
14:11:20 <lajoskatona> Before the meeting I saw 3 still unassigned bugs, ralonsoh, do you have anything you'd like to add to the report?
14:11:40 <ralonsoh> just a heads-up to review those ones unassigned
14:11:54 <lajoskatona> #link https://bugs.launchpad.net/neutron/+bug/1951816
14:12:00 <lajoskatona> #link https://bugs.launchpad.net/neutron/+bug/1951872
14:12:05 <lajoskatona> #link https://bugs.launchpad.net/neutron/+bug/1952055
14:12:11 <ralonsoh> thanks!
14:12:13 <lajoskatona> Just for the log
14:12:42 <lajoskatona> I think the first 2 was from frickler and it is in his series of testing OVN with DNS
14:13:24 <lajoskatona> I have a list of these, and I try to find somebody with more understanding of OVN to start perhaps documenting what is working and what users ca nexpect
14:14:18 <ralonsoh> I'll ping OVN folks in RH for those ones
14:14:22 <ralonsoh> (now in a meeting)
14:14:32 <lajoskatona> ralonsoh: thanks
14:14:48 <obondarev> that last one seems unrelated to neutron
14:15:57 <lajoskatona> yes the last comment from the reporter wrote: "This seems k8s related problem....."
14:16:51 <lajoskatona> ok we can move on I think
14:17:13 <lajoskatona> This week lajoskatona is the deputy, and next week amotoki will be.
14:17:26 <amotoki> lajoskatona: ack
14:17:53 <lajoskatona> I have another bugs related topic:
14:18:03 <lajoskatona> How to reduce number of rechecks - brainstorming - Mail thread started by slaweq
14:18:49 <lajoskatona> This thread was started by slaweq, please check it and if you have any other ideas how we can improve the situation please write it
14:21:42 <lajoskatona> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025813.html
14:21:51 <lajoskatona> I found finally the original mail
14:22:55 <lajoskatona> slightly related, but I thought that perhaps we can check the outreachy program to find an intern who can help with the CI related issues
14:23:02 <lajoskatona> what do you think?
14:23:31 <ralonsoh> I didn't know that was possible
14:23:51 <lajoskatona> I am not sure if we can find somebody who would like to read tons of logs for days but perhaps
14:24:21 <ralonsoh> in any case, I would like to investigate on the elastic rechecks
14:24:28 <lajoskatona> I have to check it but I think cinder (citation needed) had somebody for the previous cycle
14:25:07 <lajoskatona> ralonsoh: yeah, that seems promising also, but perhaps I have high expectations ;)
14:25:26 <ralonsoh> sure, we still need to keep watching the CI everyday
14:25:34 <mlavalle> did it work for cinder? I wonder if an intern has enough experience to help with this
14:25:35 <ralonsoh> trying to fix the neutron code
14:26:27 <lajoskatona> mlavalle: they has some results (I think it was mentioned during the what happend in the xena cycle video)
14:27:16 <lajoskatona> the goal was to remove some old shi... tech debt from cinder
14:27:55 <lajoskatona> so anyway I have to check with the organizers what we can expect from this
14:28:35 <mlavalle> well, maybe with appropriate guidance it might work. But I don't think we can get away with just outsourcing this to an intern. It will require attention from us. I'll respond in the thread
14:30:05 <lajoskatona> mlavalle: sure, it's a lot of time I suppose to mentor anybody, so it is not pure outsourcing, but perhaps with some luck it can be helpful, and I think it is good opportunity to learn
14:30:20 <mlavalle> ++
14:30:21 <lajoskatona> I mean for an intern
14:30:39 <mlavalle> maybe also for the mentor... in teaching you always learn :-)
14:30:46 <lajoskatona> ok if no objections I check it
14:30:57 <lajoskatona> mlavalle: that's true
14:32:06 <lajoskatona> I think we can jump to the next topic
14:32:44 <lajoskatona> We can skip I think L3 subteam and ryu/os-ken
14:33:00 <ralonsoh> sure
14:33:02 <lajoskatona> liuyulong is not here, and there was no change in ryu
14:33:12 <lajoskatona> #topic On Demand Agenda
14:33:23 <lajoskatona> (obondarev): Local IP feature implementation is completed, please help with reviews
14:33:34 <ralonsoh> sure
14:33:36 <obondarev> yeah, I just wanted to update the status that the feature is ready
14:33:38 <lajoskatona> https://review.opendev.org/q/topic:%22bug%252F1930200%22+status:open+project:openstack/neutron
14:33:52 <lajoskatona> \o/
14:33:54 <obondarev> I'll add a docs & release note patch
14:34:05 <obondarev> so this is a call for reviews
14:34:21 <obondarev> also a question if it needs to be added to targeted blueprints?
14:34:36 <obondarev> - probably yes, but TBH not sure what exactly it means :)
14:34:53 <lajoskatona> that's a good question
14:34:56 <mlavalle> I'd say let's add it
14:35:19 <lajoskatona> +1
14:35:24 <ralonsoh> +1
14:35:44 <obondarev> what's the procedure - should I create a blueprint for it?
14:36:10 <obondarev> as currently it's just RFE
14:37:27 <amotoki> IIUC, our rough consensus is to create a blueprint if an RFE is approved and a spec is needed (it means it is not a simple change)
14:37:29 <lajoskatona> perhaps not, just some magic in launchpad, but I have to check it with slaweq
14:37:49 <lajoskatona> ok, so we need blueprint
14:38:18 <obondarev> amotoki, lajoskatona: ok, I'll create one, thanks
14:38:58 <lajoskatona> obondarev: thanks
14:39:55 <obondarev> that's it from my side
14:40:49 <lajoskatona> thanks for the hard work on local-ip :-)
14:40:57 <ralonsoh> +1 to this
14:41:11 <obondarev> sure, many thanks for all reviewers
14:41:17 <lajoskatona> ok if there is no more topic for the on demand part we can close for today
14:42:28 <lajoskatona> #endmeeting