14:00:32 <lajoskatona> #startmeeting networking
14:00:32 <opendevmeet> Meeting started Tue Sep 14 14:00:32 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:32 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:32 <opendevmeet> The meeting name has been set to 'networking'
14:00:34 <mlavalle> o/
14:00:41 <lajoskatona> Hi everybody
14:00:52 <slaweq> hi
14:01:20 <rubasov> hi
14:01:30 <obondarev> hi
14:01:47 <manub> hi
14:02:26 <lajoskatona> I think we can start
14:02:40 <lajoskatona> #topic Announcements
14:02:57 <lajoskatona> Xena cycle calendar https://releases.openstack.org/xena/schedule.html
14:03:11 <lajoskatona> which we can close in the next weeks :-)
14:04:11 <lajoskatona> This week is RC1, and we have a lot of patches for release, please check if you have time (https://review.opendev.org/q/topic:%22xena-rc1-deadline%22+(status:open%20OR%20status:merged) )
14:04:46 <mlavalle> is that the correct url?
14:05:22 <lajoskatona> mlavalle: sorry, it seems al rc1 release patch, not only networking
14:06:45 <lajoskatona> hmmm, I will add the links to the agenda (https://wiki.openstack.org/wiki/Network/Meetings )
14:07:41 <lajoskatona> Ok, next one is the PTG, https://etherpad.opendev.org/p/neutron-yoga-ptg please add your topic please
14:08:09 <slaweq> lajoskatona: did You check opened patches for master branch? Maybe there is something important to merge before RC1 will be cut?
14:08:27 <slaweq> as if we will not merge it now, we will need to backport to Xena e.g. next week :)
14:08:47 <lajoskatona> slaweq: good point :-)
14:08:53 <slaweq> for neutron the list is https://review.opendev.org/q/project:openstack/neutron+status:open+branch:master
14:09:26 <lajoskatona> I started to check this morning few stadium projects, there is no such thing
14:10:19 <slaweq> if patch/bug isn't critical we can cut rc1 this week and backport things next week to stable/Xena branch
14:10:29 <slaweq> but we will need RC2 then :)
14:11:39 <lajoskatona> ok, I will check the open patches
14:12:48 <lajoskatona> Do You have anything more to announce or reminder to the team?
14:12:59 <obondarev> https://review.opendev.org/c/openstack/neutron/+/805366 - this one can be one candidate
14:13:10 <obondarev> to merge before rc1
14:13:37 <lajoskatona> obondarev: thanks
14:13:44 <lajoskatona> perhaps this one: https://review.opendev.org/c/openstack/neutron/+/808179
14:15:06 <slaweq> lajoskatona and others, if You have any patches like that, You can set Review-priority +2
14:15:14 <slaweq> so they will show up in the dashboard
14:15:33 <lajoskatona> sure, I will do that
14:15:37 <slaweq> ++
14:16:17 <lajoskatona> Ok so if nothing more to announcments....
14:16:29 <lajoskatona> #topic Blueprints
14:17:24 <lajoskatona> as we close Xena, that slot is empty, if You have no news about blueprints which we can discuss now
14:18:22 <lajoskatona> Ok, let's move on
14:18:26 <lajoskatona> #topic Bugs
14:18:54 <lajoskatona> Last week I was bug deputy, http://lists.openstack.org/pipermail/openstack-discuss/2021-September/024860.html
14:19:44 <lajoskatona> There was 2 bugs actually for which I asked more eyes
14:20:30 <lajoskatona> https://bugs.launchpad.net/neutron/+bug/1943355 , this one is more a question fro OVN and Neutron, and I think it was covered in the bug's comments, thanks everybody for adding thoughts
14:21:09 <lajoskatona> https://bugs.launchpad.net/neutron/+bug/1943112 and this one is a rocky deployment, which seems more a deployment issue than a Neutron bug
14:22:11 <slaweq> for me https://bugs.launchpad.net/neutron/+bug/1943112 looks also like some support request TBH
14:23:52 <obondarev> +1
14:25:24 <lajoskatona> perhaps for the deployment as well not just for Neutron itself from the last comment
14:26:58 <lajoskatona> I try to ask more if we can direct the user to the good direction.
14:27:34 <lajoskatona> Ok, This week amotoki is the bug deputy
14:28:07 <lajoskatona> and the next week is for bcafarel, am I right ?
14:28:21 <slaweq> yes :)
14:28:35 <lajoskatona> ok, than I followed the switches :-)
14:29:55 <lajoskatona> If nothing more for bugs we can move on
14:30:06 <slaweq> ++
14:30:07 <lajoskatona> #topic On Demand Agenda
14:30:40 <lajoskatona> I added a small topic regarding os-ken/ryu
14:31:22 <lajoskatona> I realized that ryu from which we forked os-ken is active: https://github.com/faucetsdn/ryu
14:31:58 <lajoskatona> and would like to know hwta do you think about reaching out to them to discuss if we can collaborate
14:32:56 <lajoskatona> most of os-ken is dead code for Neutron, and we maintain it, perhaps we can have a way to bring in some more people to maintain it and bring new ideas/features
14:34:03 <lajoskatona> of course it's possible that the ryu "team" just happy how they work now and not interested in it, but wanted to hear some opinions from Neutron side
14:34:30 <mlavalle> that's probably worth exploring. We shpould keep in mind that the reason we created os-ken is that the ryu team said they were not going to develop / support their framework anymore
14:34:52 <mlavalle> and they didn't want us to depoend on them
14:35:03 <mlavalle> but maybe things have changed lately
14:35:15 <mlavalle> we don't loose anything by asking
14:36:21 <lajoskatona> +1
14:36:46 <slaweq> +1
14:36:52 <lajoskatona> Not sure if this is the same team now, the github page's owner is Faucet Foundation ( https://www.faucet.org.nz/ )
14:38:56 <lajoskatona> ok than I try to contact them
14:39:46 <lajoskatona> If no more things to discuss, I think we can close the meeting
14:40:01 <slaweq> great job lajoskatona :)
14:40:03 <slaweq> thx
14:40:08 <lajoskatona> Have a great week
14:40:15 <lajoskatona> #endmeeting