14:00:29 <lajoskatona> #startmeeting networking
14:00:29 <opendevmeet> Meeting started Tue Nov  9 14:00:29 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:29 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:29 <opendevmeet> The meeting name has been set to 'networking'
14:00:32 <lajoskatona> Hi
14:00:35 <obondarev> hi
14:00:38 <mlavalle> o/
14:00:44 <isabek> Hi
14:00:49 <bcafarel> hi
14:00:49 <rubasov> o/
14:02:02 <lajoskatona> Let's start
14:02:04 <lajoskatona> #topic Announcements
14:02:18 <lajoskatona> Yoga cycle calendar #link https://releases.openstack.org/yoga/schedule.html
14:02:26 <slaweq> hi
14:03:01 <lajoskatona> This week is the final week for Ussuri, so if you have anything to merge and release for ussuri please push that
14:03:17 <amotoki> hi
14:03:40 <lajoskatona> we have one patch series hanging: https://review.opendev.org/q/I409bc674b65e4f495ebd42d03e97a09d51482339
14:04:06 <lajoskatona> Hi slaweq & amotoki :-)
14:04:11 <bcafarel> yes apart from it it looks good: https://review.opendev.org/q/project:openstack/neutron+branch:stable/ussuri+status:open
14:04:54 <lajoskatona> bcafarel: thanks
14:05:33 <lajoskatona> We have to propose last release patch for ussuri ( Iahve to check if isn't there an automatic one already)
14:06:17 <lajoskatona> and actually that's all announcements from me, do you have anything in mind or questions for announcements?
14:06:35 <lajoskatona> ohh, no I have few more lines....
14:06:55 <lajoskatona> CI meeting time slot: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025578.html please vote, if you a fan of the CI meeting ;)
14:07:12 <slaweq> ++
14:07:23 <lajoskatona> And I sent out a vote for the team meeting as well: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025702.html
14:07:32 <lajoskatona> and for the drivers meeting: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025705.html
14:07:59 <lajoskatona> I thought that next week we can discuss the results for the last 2
14:08:14 <lajoskatona> slaweq: whan we will have final result for CI meeting slot?
14:08:30 <slaweq> I though to summarize it this week
14:08:43 <slaweq> so let's say that deadline is end of this week
14:08:48 <lajoskatona> slaweq: ok, thanks,
14:09:18 <lajoskatona> ok, so if nothing more for announcements.....
14:09:48 <lajoskatona> # topic Community Goals
14:10:20 <mlavalle> so no meeting times change this week, right?
14:10:28 <lajoskatona> on this meeting we have't discussed community goals recently, but RBAC was a hot and long topic on the PTG....
14:10:54 <lajoskatona> mlavalle: next weeks meeting will be the same time
14:11:05 <mlavalle> ack
14:11:30 <lajoskatona> so for communit goals there was a mail from last meeting of TC: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025693.html
14:11:57 <lajoskatona> and they linked the etherpad for RBAC discussion an etherpad with notes: #link https://etherpad.opendev.org/p/policy-popup-yoga-ptg
14:12:55 <lajoskatona> to tell the truth I haven't read it in details, so it is more a headsup that there should be finally some outcome of how to handle system scopes and related things.....
14:13:48 <lajoskatona> Do you have some comments, question for the RBAC and community goal for Yoga cycle?
14:14:03 <amotoki> perhaps we can focus on improving system-scope related things in neutron side.
14:14:04 <mlavalle> so hold for now, right?
14:14:35 <lajoskatona> amotoki: sure, but to tell the truth I lost what is the direction....
14:14:37 <amotoki> and we can reflect openstack-wide discussion results to our implementations if needed
14:15:47 <amotoki> lajoskatona: the last week discussion was mainly focused on how to handle project-specific resources with system-scoped token, but it is still unclear to me....
14:15:50 <lajoskatona> amotoki: +1, that makes things easier for sure, and we have painpoints  where nova-neutron interaction is in question for example
14:16:20 <slaweq> amotoki: I wanted to do that but I'm still not sure how new rules should looks like
14:16:24 <lajoskatona> amotoki: you saved my day, I thought I am the last one who understands half of this whole topic :-)
14:16:47 <amotoki> slaweq: me neither :(
14:17:02 <slaweq> IIUC we should have system_scope only for APIs like for agents or logs maybe
14:17:19 <slaweq> only things which don't really have project_id
14:17:33 <slaweq> but there should be also some new persona IIUC
14:17:53 <slaweq> so I would like to change all at once and that's why I didn't moving on with this yet
14:18:29 <lajoskatona> slaweq, amotoki: thanks for keeping an eye on this topic
14:19:00 <amotoki> slaweq: my undrestanding is same (though I am not sure I caught the discusion fully) but I agree we should wait till the direction is clear.
14:19:29 <slaweq> ++
14:20:10 <lajoskatona> ok, so as mlavalle said: hold for now, till we have clear direction
14:20:53 <lajoskatona> ok if nothing more for RBAC and community goals, let's move on
14:21:30 <lajoskatona> #topic Bugs
14:21:42 <lajoskatona> bcfarel was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025703.html
14:22:30 <lajoskatona> From the mail it seems that every bug is handled, bcafarel: do you have anything to add?
14:23:20 <bcafarel> no, all bugs have good progress or assignee in that week :)
14:23:41 <lajoskatona> bcafarel: thanks for the report :-)
14:23:54 <lajoskatona> This week slaweq is the deputy, and next week hongbin will be.
14:24:05 <slaweq> I'm on it already :)
14:24:12 <lajoskatona> slaweq: thanks
14:24:36 <lajoskatona> I will write a mail to hongbin to be sure
14:24:47 <lajoskatona> ok next topic
14:24:49 <lajoskatona> #topic L3 subteam
14:24:57 <lajoskatona> #link https://wiki.openstack.org/wiki/Network/Meetings#L3_subteam
14:25:43 <lajoskatona> liuyulong collected a lot of blueprints to the wiki, but I can't see him
14:27:38 <lajoskatona> some of them are already finished, like ECMP support....
14:29:03 <lajoskatona> as liuyulong is not here, I think we can move forward
14:29:18 <lajoskatona> #topic ryu and os-ken
14:29:25 <lajoskatona> #link https://etherpad.opendev.org/p/make_os-ken_and_ryu_sync
14:29:36 <slaweq> there is no ralonsoh  today so I guess no update
14:29:50 <lajoskatona> no new patches in ryu this week, so we can close this
14:29:53 <slaweq> but good news is that we merged all backports from ryu to os-ken last week
14:30:15 <lajoskatona> yes exactly and we have an os-ken release with them
14:30:26 <slaweq> yes
14:30:47 <lajoskatona> #topic On Demand Agenda
14:31:07 <lajoskatona> I added a topic, but I am more the post man for it:
14:31:14 <lajoskatona> What to move to neutron-lib?
14:31:46 <lajoskatona> There is an interesting debate over few patches what code parts/ constants etc to move to n-lib:
14:31:53 <lajoskatona> https://review.opendev.org/c/openstack/neutron/+/797121
14:32:06 <lajoskatona> https://review.opendev.org/c/openstack/neutron/+/797120
14:32:11 <lajoskatona> https://review.opendev.org/c/openstack/neutron-lib/+/807224
14:32:26 <lajoskatona> I hope I collected all of the relevant patches :-)
14:32:36 <slaweq> yes, thx
14:32:56 <slaweq> actually https://review.opendev.org/c/openstack/neutron/+/797120 and https://review.opendev.org/c/openstack/neutron-lib/+/807224 are important in that discussion
14:33:09 <slaweq> basically I wanted to move all ovs constants to the neutron-lib
14:33:18 <lajoskatona> liuyulong is on this discussion so sad that we can't have him
14:33:26 <slaweq> as e.g. some of them were (are) used by networking-bagpipe IIRC
14:33:34 <slaweq> and all of them are rehomed already
14:33:53 <slaweq> now liuyulong wants to keep *ALL_TABLES lists in the neutron
14:34:05 <slaweq> as it may "speed" development process in some cases
14:34:34 <slaweq> but obondarev had IMO very good point that if we will keep those lists separately, in the future we will forget to add new tables to it
14:34:49 <slaweq> so it's better to move all to neutron-lib and use it from neutron-lib
14:35:11 <slaweq> and now I think we need some more votes to judge which approach would be better :)
14:36:14 <obondarev> slaweq: do you know which constants are used by networking-bagpipe? Maybe we should move only those constants that are known to be used by 2+ projects?
14:36:17 <lajoskatona> I think this is that comment and discussion under it: https://review.opendev.org/c/openstack/neutron/+/797120/comment/41ae240e_35fcd1b2/
14:37:31 <slaweq> yes
14:38:38 <obondarev> such "common" constants will be saved in lib and used by other projects. Specific constants may stay in specific repos until needed by someone else
14:39:07 <obondarev> I think that was the workflow for neutron-lib originally
14:39:12 <lajoskatona> obondarev: +1
14:39:49 <amotoki> yeah, that is the principle. in case of OF tables, we need to avoid conflicts among table numbers. I think that's the point.
14:40:57 <slaweq> yes
14:41:13 <obondarev> good point
14:41:28 <mlavalle> +1
14:42:46 <slaweq> if You'll have some time, please comment on that patch
14:42:58 <slaweq> so I can move on with it in one or another way :)
14:43:00 <slaweq> thx a lot
14:43:20 <lajoskatona> so let's revisit these changes and follow the "old" rule: move only things that used by multiple projects, otherwise avoid conflicts in places like OF tables.
14:43:36 <lajoskatona> Can that be the summary?
14:43:49 <slaweq> yes
14:44:47 <lajoskatona> ok, than I think we can close this dicussion here, and continue under the reviews, I will point it to ralonsoh and liuyulong to have all of us on the same page
14:45:34 <slaweq> ++ thx
14:45:46 <lajoskatona> If no more topics for the On Demand agenda.....
14:45:50 <dmitriis> looking for a second core review on https://review.opendev.org/c/openstack/neutron-specs/+/788821/ if anybody has cycles for it.
14:47:29 <dmitriis> Liu looked at it but only gave a +1 so I guess it has to be somebody else
14:48:00 <lajoskatona> yes, please if you have time to review this spec, check it, as it is again a cross-project effort with Nova and with OVN (out of our control) and nova waits for the neutron-spec review
14:48:01 <mlavalle> I'll look at it later today
14:48:16 <dmitriis> tyvm
14:48:20 <lajoskatona> mlavalle: thanks
14:48:59 <lajoskatona> if nothing more.....
14:49:26 <lajoskatona> #endmeeting