14:00:18 <lajoskatona> #startmeeting networking
14:00:18 <opendevmeet> Meeting started Tue Jul 19 14:00:18 2022 UTC and is due to finish in 60 minutes.  The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:18 <opendevmeet> The meeting name has been set to 'networking'
14:00:19 <mlavalle> o/
14:00:21 <lajoskatona> Hi
14:00:27 <obondarev> hi
14:00:30 <isabek> hi!
14:01:21 <slaweq> hi
14:01:30 <bcafarel> o/
14:01:41 <haleyb_> hi
14:02:13 <lajoskatona> I think we can start now
14:02:17 <lajoskatona> #topic Announcements
14:02:24 <ralonsoh> hi
14:02:24 <lajoskatona> the usual Zed schedule: https://releases.openstack.org/zed/schedule.html
14:02:44 <lajoskatona> elodilles sent a nice mail for the comming weeks schedule:
14:02:49 <lajoskatona> [release] Release countdown for week R-11, Jul 18 - 22: (#link https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029583.html)
14:03:03 <lajoskatona> and was also kind to do a summary at end of the mail for lazy PTLs:
14:03:10 <lajoskatona> Non-client library freeze: August 26th, 2022 (R-6 week)
14:03:25 <lajoskatona> Client library freeze: September 1st, 2022 (R-5 week)
14:03:30 <lajoskatona> Zed-3 milestone: September 1st, 2022 (R-5 week)
14:03:58 <lajoskatona> so we are close to the final weeks of the Zed cycle
14:04:11 <slaweq> time flies
14:04:27 <lajoskatona> sad but true :-)
14:04:42 <lajoskatona> Related topic: Spec reviews please!
14:04:47 <lajoskatona> https://review.opendev.org/q/project:openstack/neutron-specs+status:open+-age:1week
14:05:03 <lajoskatona> there are some older specs also, but without much change
14:05:18 <lajoskatona> this list should give the active reviews
14:06:14 <slaweq> ++
14:07:00 <lajoskatona> As this cycle goes we can vote for the name of the next one:
14:07:04 <lajoskatona> https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029608.html
14:07:40 <lajoskatona> this morning the antelope was the winner, but I like better anteater as ants are nearly bugs....
14:07:59 <ykarel> o/
14:08:53 <slaweq> LOL
14:09:05 <slaweq> I voted for antelope - sorry :)
14:09:39 <lajoskatona> And even the PTG is comming, so I got a mail from Kendall about "Operator Engagement at the PTG"
14:09:45 <amotoki> voting is still open. let's vote :-)
14:10:12 <bcafarel> poor anteater
14:10:14 <lajoskatona> amotoki: thanks, yes the voting is open till tomorow perhaps
14:11:37 <lajoskatona> so for the PTG the organizers expect us (me) to collect some answer for these questions:
14:11:43 <lajoskatona> What do you want to hear from operators about at the PTG?
14:11:48 <lajoskatona> What topics are already on your agenda?
14:11:54 <lajoskatona> What are your goals for the Columbus PTG?
14:12:00 <lajoskatona> If there was an extra day (Friday, October 21 of Operator sessions), would contributors from your team be interested in participating?
14:12:44 <lajoskatona> so if you have some time please think on these questions
14:12:49 <slaweq> regarding last question, I'm definitely interested
14:13:08 <mlavalle> how do we submit ansers?
14:13:08 <slaweq> maybe You can create e.g. etherpad where everyone can answer to those questions
14:13:23 <mlavalle> yeah, etherpad is a good idea
14:13:24 <lajoskatona> slaweq: yes, thats good idea
14:13:49 <lajoskatona> perhaps I open the usual PTG planning pad, and we can add this topic to that
14:14:01 <slaweq> ++
14:14:07 <mlavalle> yes
14:15:01 <lajoskatona> by the way who is planning to go to Colombus PTG?
14:15:41 <lajoskatona> With rubasov (and elodilles) we started the organization, but it is summer time so slooooowwww everything
14:15:48 <slaweq> If I will be able to, I definitely want to go
14:15:54 <lajoskatona> I mean organization for travel
14:16:03 <lajoskatona> slaweq: +1
14:16:09 <slaweq> but nothing is decided internally yet AFAIK
14:16:20 <mlavalle> same here
14:16:21 <ralonsoh> same here
14:16:33 <mlavalle> what are the dates?
14:16:42 <ralonsoh> 16-21 Oct
14:16:53 <ralonsoh> 17-20, to be precise
14:16:54 <lajoskatona> yeah we are waiting for approval also
14:17:04 <lajoskatona> ralonsoh: +1, thanks
14:17:14 * mlavalle will bring this up during my next 1 on 1
14:17:47 <lajoskatona> ok, that's all for announcements from me
14:18:59 <lajoskatona> #topic Community Goals
14:19:36 <lajoskatona> Actually I just would like to ask perhaps slaweq if he has some time for next meeting for example to give a quick summary what we supposed to do with rbac
14:19:51 <slaweq> sure
14:20:01 <slaweq> I can do it even now if You want
14:20:15 <lajoskatona> slaweq: thanks, if you can that would be cool
14:20:25 <lajoskatona> sorry for not warning before
14:20:29 <slaweq> basically there is proposal to change goal slightly https://review.opendev.org/c/openstack/governance/+/847418
14:20:58 <lajoskatona> yeah Iread it before the meeting and I realised that something is happening
14:21:06 <slaweq> we will need to do (again) some changes in Neutron to remove "scope=['system']" from everywhere and have only scope "project" available
14:21:30 <slaweq> but I didn't propose patches yet as I want to have this change approved and merged first
14:21:38 <lajoskatona> slaweq: +1
14:21:58 <lajoskatona> and if I understand well we keep also the "old" admin ?
14:22:15 <slaweq> tl;dr it's because we realized during last summit, that operators don't really need system_scope users (for now at least), it can be confusing for them and it is causing a lot of problems
14:22:26 <slaweq> yes, so we will keep an "old" admin
14:22:35 <slaweq> and we will have project_member and project_reader
14:22:40 <amotoki> yes, the latest proposal is to introduce well-defined personas (as roles) only
14:23:02 <lajoskatona> slaweq, amotoki: thanks
14:23:07 <slaweq> and later we will have "project_manager" which will be kind of the same thing as "project_admin" in the current approach
14:23:11 <mlavalle> so we over-engineered vs what the community needed
14:23:19 <slaweq> mlavalle: kind of
14:23:30 <slaweq> at least as a first step of the goal
14:23:43 <slaweq> system scope personas is good idea but maybe for future, not now
14:24:04 <slaweq> so that's basically all regarding S-RBAC
14:24:06 <slaweq> any questions/comments?
14:24:46 <lajoskatona> slaweq: thanks for the summary
14:24:56 <mlavalle> are we having to restore any of the functionality that the community really needs?
14:25:16 <slaweq> mlavalle: I'm not sure I understand Your questions
14:25:23 <mlavalle> Or is it just a matter of not merging or removing not needed stuff?
14:25:37 <slaweq> we will need to change things which are already merged
14:25:53 <slaweq> as we were one of the projects who already implemented system scope personas some time ago
14:26:02 <slaweq> but we never switched to use them as default
14:26:15 <mlavalle> that answers my question
14:26:25 <mlavalle> deployers won't see a gap on what they need
14:26:33 <slaweq> it's on my radar and I will do it but when new direction will be approved
14:26:46 <mlavalle> it's just that new stuff was never adopted
14:27:12 <slaweq> yes
14:29:14 <lajoskatona> ok, thanks for the quick recap on what's happenning with the sRBAC
14:29:49 <lajoskatona> #topic Bugs
14:29:57 <lajoskatona> Report from jlibosva: https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029618.html
14:30:19 <lajoskatona> I would like to highlight one from the 2:
14:30:22 <lajoskatona> Some jobs broken post pyroute2 update to 0.7.1 (#link https://bugs.launchpad.net/neutron/+bug/1981963 )
14:31:04 <slaweq> yeah, I saw it today
14:31:12 <ralonsoh> we need https://review.opendev.org/c/openstack/requirements/+/850295
14:31:19 <slaweq> it seems that dvr jobs and functional job are broken due to that
14:31:20 <lajoskatona> it is due to recent pyroute2 release, and there are 2 isssues opened on pyroute2
14:31:35 <ralonsoh> tomorrow we'll have 0.7.2 and I'll push a requirements patch to bump to this new version
14:32:02 <lajoskatona> ralonsoh: thanks
14:32:07 <mlavalle> ++
14:32:29 <lajoskatona> slaweq: and octavia is also broken due to this version of pyroute2
14:33:01 <slaweq> thx ralonsoh and gthiemonge for fixes in pyroute2
14:33:10 <ykarel> but seems we using upper-constraints everywhere in neutron, right?
14:34:05 <ykarel> asking if https://review.opendev.org/c/openstack/requirements/+/850295 needed to unblock something or just to get it block so it doesn't get pulled where upper constraints is not used
14:34:05 <ralonsoh> yes, we do
14:34:21 <ralonsoh> to fix octavia
14:34:31 <ralonsoh> and prevent neutron from pulling a borken version
14:34:37 <ralonsoh> broken*
14:34:38 <ykarel> okk ok got it
14:34:51 <ykarel> likely octavia is not using u-c in some jobs
14:35:40 <ralonsoh> (that's something that needs to be checked, for sure)
14:36:19 <johnsom> I would be surprised if there are Octavia jobs not using upper-constraints (other than those intended to test with master branches).
14:37:19 <ykarel> or i think requirements-check job is that which can be impacted
14:39:16 <lajoskatona> I think we can move on if there is no more questions for the bugs
14:39:24 <ykarel> +1
14:39:33 <lajoskatona> This week obondarev is the deputy and next week isabek will be.
14:39:42 <obondarev> on it
14:39:44 <isabek> o/
14:39:54 <lajoskatona> obondarev, isabek: thanks
14:40:00 <lajoskatona> #topic On Demand Agenda
14:40:11 <lajoskatona> Do you have anything which we can discuss?
14:40:46 <slaweq> nothing from me
14:41:49 <lajoskatona> if nothing we can close the meeting
14:41:57 <lajoskatona> #endmeeting