14:01:27 <ralonsoh> #startmeeting networking
14:01:27 <opendevmeet> Meeting started Tue Feb 14 14:01:27 2023 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:27 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:27 <opendevmeet> The meeting name has been set to 'networking'
14:01:29 <elvira> o/
14:01:29 <ralonsoh> hello all
14:01:32 <obondarev> hi
14:01:36 <lajoskatona> o/
14:01:37 <frickler> \o
14:02:12 <sahid> o/
14:02:31 <bcafarel> o/
14:02:37 <ykarel> o/
14:02:46 <ralonsoh> ok, let's start
14:02:48 * mlavalle is an internal company meeting. will lurk in the background
14:02:56 <ralonsoh> #topic announcements
14:03:02 <ralonsoh> Antelope / 2023.1 schedule: https://releases.openstack.org/antelope/schedule.html
14:03:21 <ralonsoh> this week is R-5
14:03:23 <slaweq> o/
14:03:31 <ralonsoh> and that is antelope-3 milestone
14:03:50 <ralonsoh> remember this he final release for client libraries
14:03:54 <ralonsoh> and the feature freeze
14:04:09 <ralonsoh> the RC1 will be in 2 weeks
14:04:35 <ralonsoh> also remember that you have time to propose your candidacy for Neutron PTL (and other projects)
14:04:52 <ralonsoh> please check the calendar in https://governance.openstack.org/election/
14:05:21 <ralonsoh> and a couple of needed links for the next PTG
14:05:28 <ralonsoh> Bobcat etherpad: https://etherpad.opendev.org/p/neutron-bobcat-ptg
14:05:35 <lajoskatona> \o/
14:05:46 <ralonsoh> please start adding your topics to the Bobcat Neutron etherpad
14:05:58 <lajoskatona> +1
14:06:10 <ralonsoh> during the next meetings, we'll check them and make the schedule
14:06:45 <ralonsoh> I'll remember this link every week
14:07:05 <ralonsoh> I also want to talk about the Vancouver meeting
14:07:21 <ralonsoh> but, if you don't mind, I'll move this topic to the "on demand" section
14:07:41 <lajoskatona> ok, I anyway added the advertisement for Vancouver forum proposals
14:07:55 <ralonsoh> lajoskatona, of course!
14:07:59 <lajoskatona> I mean I added to the on-demand agenda
14:08:36 <ralonsoh> right, I didn't see that
14:08:37 <ralonsoh> cool
14:09:08 <ralonsoh> and as usual, please check https://openinfra.dev/live/#all-episodes
14:10:00 <ralonsoh> ok, I think I'm not missing anything
14:10:17 <ralonsoh> related to the release schedule or anything
14:10:46 <ralonsoh> ok, let's move to the next topic then
14:10:52 <ralonsoh> #topic bugs
14:11:08 <ralonsoh> last week report is from elvira
14:11:16 <ralonsoh> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032167.html
14:11:32 <ralonsoh> so far, there are some bugs still not assigned
14:11:48 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2006953
14:11:59 <ralonsoh> I think ykarel has sent a patch recently
14:12:08 <ykarel> yes
14:12:11 <ralonsoh> right: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/873708
14:12:20 <ralonsoh> ok thanks!
14:12:43 <ralonsoh> ahhh ok, I see the issue, thanks!
14:13:05 <ralonsoh> then next one is
14:13:06 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2006683
14:13:15 <ralonsoh> but I think ykarel sent another patch
14:13:25 <ykarel> no lajoskatona sent it
14:13:30 <ralonsoh> ah yes
14:13:34 <ralonsoh> and is merged now: https://review.opendev.org/c/openstack/neutron-fwaas/+/873360
14:13:39 <ralonsoh> (cool)
14:13:40 <ykarel> but not full fix
14:14:14 <ralonsoh> what else is missing?
14:14:17 <ykarel> i commented there https://bugs.launchpad.net/neutron/+bug/2006683/comments/3, can you check if that makes sense
14:14:26 <lajoskatona> exactly, I saw this in the logs  but I am sure that it will not solve all issues, just cleans th log before the exact traceback
14:15:22 <lajoskatona> ykarel: I check your comment later, I missed that
14:15:34 <ralonsoh> ok so we are still seeing txn errors
14:15:42 <ralonsoh> due to the slqalchemy migration
14:16:14 <lajoskatona> yeah, but as I see sqalchemy2 will not be "included", at least the req bump patch is still red
14:16:33 <lajoskatona> and bauzas from Nova asked to skip it
14:16:34 <ykarel> lajoskatona, ack, we can check few more runs if it's sees again with your fix included
14:16:54 <ykarel> yes the current failures are with sqlalchmey-1.4
14:17:29 <ralonsoh> in any case, we need to check what is the txn that is failing, or the operation
14:17:37 <ralonsoh> let's keep an eye on this one
14:17:41 <ykarel> +1
14:17:44 <lajoskatona> +1
14:18:01 <ralonsoh> the last one I had is
14:18:04 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2006145
14:18:57 <lajoskatona> this one is for neutron-dynamic-routing as I see
14:18:58 <ralonsoh> maybe ltomasbo ^^ can help us on this one
14:19:39 <frickler> I'll take a look, too.
14:19:58 <ralonsoh> but I would say that what they are testing could not be supported
14:20:00 <frickler> I see the use case, otoh the current system is kind of working as designed
14:20:17 <ralonsoh> they are manually stopping the RPC communication
14:20:28 <ralonsoh> frickler, it is?
14:21:01 <frickler> well the current implementation assumes that rmq is always available
14:21:06 <ralonsoh> right
14:21:08 <frickler> that's why we have HA for it
14:21:30 <frickler> but if operators really need to shut it down for upgrades, we could try to adapt for that
14:21:49 <ralonsoh> so that could be a RFE, not a bug
14:22:00 <frickler> yes, I agree to that
14:22:10 <ralonsoh> perfect, do you mind commenting on the bug?
14:22:22 <frickler> I also wonder how everything else in openstack handles an rmq outage
14:22:34 <ltomasbo> frickler, ralonsoh: I know when using FRR you have some options to keep those routes. As NDR has its own speaker implementation, I suppose either that needs to be enabled (or added if missing)
14:22:34 <frickler> I'll have a look at the code and then comment, yes
14:23:18 <ralonsoh> other agents (OVS, DHCP, etc) keep running if no info from the server is needed
14:23:32 * mlavalle back in the meeting
14:23:35 <ralonsoh> of course, if they need to request something from the server, the operation will stop
14:23:47 <frickler> don't they do periodic refresh, too?
14:24:08 <ralonsoh> they do heartbeats
14:24:15 <ralonsoh> but that doesn't stop the agent
14:24:23 <ralonsoh> if the need to do a resync, then yes
14:25:10 <ralonsoh> in any case, I would need to check the ndr agent code too
14:25:37 <frickler> yes, let's dig a bit and come back to it next week or outside the meeting
14:25:48 <ralonsoh> frickler, ltomasbo thanks for the info
14:26:19 <ralonsoh> This week ykarel is the deputy, next week will be bcafarel (mtomaska can't next week)
14:26:23 <ykarel> yes
14:26:45 <bcafarel> ralonsoh: ack thanks for the reminder!
14:26:59 <ralonsoh> just a heads-up: we are experiencing random issues in the CI, more frequent as before
14:27:11 <ralonsoh> we will talk about this during the CI meeting
14:27:24 <ralonsoh> I know ykarel has addressed some of them during this week
14:27:45 <ralonsoh> but we need, somehow, to stabilize the CI
14:28:21 <ralonsoh> ok, let's move to the next topic
14:28:25 <ralonsoh> #topic specs
14:28:32 <ralonsoh> the only one open (an active) is
14:28:35 <ralonsoh> #link https://review.opendev.org/c/openstack/neutron-specs/+/870030
14:28:53 <ralonsoh> I've been following the discussion between Dmitrii and lajoskatona
14:29:46 <ralonsoh> I still need to check some of the new API changes and the architecture
14:29:59 <ralonsoh> but I don't think we should merge it in this cycle
14:30:01 <lajoskatona> as I see there are open topics for those items
14:30:09 <ralonsoh> right
14:30:19 <lajoskatona> agree, but the progress and responsibility is good as I see
14:30:52 <ralonsoh> for sure and that will be attended during the next cycle without nay doubt
14:31:04 <ralonsoh> IMO, the spec is close to be ready
14:31:07 <ralonsoh> but not this week
14:31:18 <ralonsoh> so I'll add a comment today
14:31:48 <ralonsoh> that's all on this topic
14:31:56 <ralonsoh> let's move to the next
14:31:59 <ralonsoh> next one
14:32:00 <ralonsoh> #
14:32:05 <ralonsoh> (uffff)
14:32:18 <ralonsoh> #topic community_goals
14:32:25 <ralonsoh> 1) Consistent and Secure Default RBAC
14:32:31 <ralonsoh> #link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/867518
14:32:42 <ralonsoh> slaweq has done a fantastic job during this release
14:32:53 <ralonsoh> should we merge this patch ^^ now?
14:33:06 <ralonsoh> or should we wait 2 weeks?
14:33:28 <ralonsoh> slaweq ^
14:34:11 <ralonsoh> (I think he is in other meeting at the same time)
14:34:22 <bcafarel> how stable is the job? (or should be)
14:34:37 <bcafarel> mostly thinking of CI stability these days :)
14:34:40 <ralonsoh> it is quite stable
14:34:54 <ralonsoh> a couple of failures in fwaas and bgp
14:35:02 <ralonsoh> but seems stable
14:35:03 <lajoskatona> I think instability is not coming from this now but from general issues in all other jobs
14:35:08 <slaweq> this job is pretty stable
14:35:10 <slaweq> the same as all other similar jobs
14:35:12 <slaweq> yes, I agree
14:35:12 <ralonsoh> lajoskatona, right
14:35:30 <ralonsoh> ok, then I'll change my vote on this one
14:35:31 <slaweq> those neutron-tempest-plugin-xxx jobs are IMHO one of the most stable once recently :)
14:35:37 <ralonsoh> yes
14:35:48 <slaweq> ++
14:35:50 <bcafarel> if it stable big +1 to have it running and seeing results already on these (before switching next cycle)
14:35:53 <slaweq> thx
14:36:00 <ralonsoh> perfect
14:36:16 <slaweq> will be good to have it now so we will also have it in stable/anthelope later :)
14:36:37 <ralonsoh> ok, I've increased the review priority
14:37:08 <slaweq> in next cycle we will change it to be only job running with "old default policies" as we will switch to use new ones by default
14:37:40 <ralonsoh> perfect so new ones will be the default ones
14:38:04 <slaweq> in 2023.2 yes
14:38:17 <slaweq> in 2023.1 we will have one job which will test them
14:39:02 <ralonsoh> just out of curiosity, what is the status of other projects?
14:39:35 <slaweq> gmann knows it the best but AFAIK nova, glance, cinder are all good to switch also
14:39:42 <slaweq> and keystone of course
14:39:53 <slaweq> I don't really know much about other projects
14:40:13 <ralonsoh> good to know that big projects are on track too
14:40:36 <slaweq> https://review.opendev.org/q/topic:secure-rbac
14:40:46 <slaweq> there is many patches in that topic :)
14:41:31 <ralonsoh> ok, in some weeks we'll swap to the new policies by default
14:41:37 <slaweq> yes
14:41:48 <ralonsoh> perfect, we'll check at this time then
14:41:50 <ralonsoh> thanks!
14:42:11 <ralonsoh> the next sub-topic is
14:42:13 <ralonsoh> 2) Neutron client deprecation
14:42:21 <ralonsoh> lajoskatona, we have new releases, right?
14:42:24 <lajoskatona> Actually no news from my side
14:42:31 <ralonsoh> so we can continue with some patches now
14:42:49 <lajoskatona> perhaps one is htat I was waiting for SDK release, but as it is now out the req bump is still missing
14:42:56 <ralonsoh> ah right
14:43:02 <ralonsoh> (I always forget that second step)
14:43:08 <ralonsoh> never mind
14:43:26 <ralonsoh> ok, thanks lajoskatona!
14:43:27 <lajoskatona> So that is true for other libs also, we have releases finally but we still waiting for he u-c files to be upgraded
14:44:21 <ralonsoh> and the last topic for today is
14:44:25 <ralonsoh> #topic on_demand
14:44:28 <ralonsoh> lajoskatona, please
14:44:51 <lajoskatona> I just wanted to advertise the possibilty to propose forum topics for the summit
14:45:03 <ralonsoh> #link https://etherpad.opendev.org/p/neutron-bobcat-ptg
14:45:26 <lajoskatona> I think the forum schedule will be finalized mid April, and I suppose we have topropose before that
14:45:46 <lajoskatona> https://openinfra.dev/summit/vancouver-2023/forum/
14:45:46 <slaweq> good point lajoskatona
14:45:50 <mlavalle> Thanks for the reminder
14:45:53 <ralonsoh> yeah, aboyt this
14:45:55 <ralonsoh> one sec
14:46:06 <slaweq> maybe we can open another etherpad to collect some ideas there
14:46:08 <ralonsoh> I opened this second etherpad
14:46:09 <ralonsoh> https://etherpad.opendev.org/p/neutron-vancouver-2023
14:46:11 <ralonsoh> ^^^
14:46:18 <slaweq> ralonsoh++
14:46:33 <lajoskatona> thanks, +1
14:46:45 <ralonsoh> so that's the point: what kind of topics are we going to discuss in Vancouver (after the virtual PTG)?
14:47:23 <ralonsoh> the PTG is in March, Vancouver summit is in June (3 months)
14:47:54 <slaweq> ralonsoh I think that those are 2 different things: one is our "ptg" in vancouver and second are topics for the forum session, to e.g. collect feedback from operators, etc.
14:47:56 <slaweq> but we can use the same etherpad for now to collect ideas for both
14:48:31 <ralonsoh> right, we can open different topics in the agenda
14:48:52 <lajoskatona> agree, but I see the Vancouve mid-cycle meeting as a frre to use opportuninty for disccusion
14:49:03 <ralonsoh> in any case, I'll send a mail today with both links
14:49:13 <ralonsoh> just to make it public for everyone
14:49:13 <lajoskatona> but an agenda is good idea
14:50:01 <ralonsoh> to be honest (but this is my opinion) I don't see the relevance of the Vancouver PTG
14:51:14 <ralonsoh> anyway, as commented, I'll send a mail today with both agendas
14:51:26 <frickler> +1, excluding the non-travelling part of the community isn't a good idea IMO
14:51:26 <lajoskatona> +1
14:52:19 <lajoskatona> yeah but the meeting opprotunity is good, and I hope there will be option to have it hybrid
14:52:36 <ralonsoh> I agree on this
14:53:54 <ralonsoh> ok folks, is there anything else to be discussed today?
14:54:07 <ralonsoh> (please remember the CI meeting in 6 minutes)
14:54:20 <slaweq> ++
14:54:33 <slaweq> see You in few minutes on CI meeting
14:54:34 <ralonsoh> see you there! bye
14:54:39 <ralonsoh> #endmeeting