14:03:49 <lajoskatona> #startmeeting networking
14:03:49 <opendevmeet> Meeting started Tue Mar  1 14:03:49 2022 UTC and is due to finish in 60 minutes.  The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:03:49 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:03:49 <opendevmeet> The meeting name has been set to 'networking'
14:03:59 <lajoskatona> Hi
14:04:06 <ralonsoh> hi
14:04:08 <elvira> o/
14:04:16 <mlavalle> o/
14:04:23 <lajoskatona> amotoki: in a few weeks it will be no problem as we change to summer time here
14:04:56 <ykarel> o/
14:05:02 <amotoki> lajoskatona: nice! joking :-)
14:05:28 <bcafarel> o/
14:05:31 <rubasov> o/
14:06:10 <slaweq> o/
14:06:11 <liuyulong> hi
14:06:21 <lajoskatona> #topic Announcements
14:06:40 <lajoskatona> Release countdown, R-4: #link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027422.html
14:06:58 <lajoskatona> Yoga branch cut on its way for some projects: https://review.opendev.org/c/openstack/releases/+/831289
14:07:17 <lajoskatona> I also have to check it :-)
14:09:18 <lajoskatona> From the mail: RC1 deadline: March 10th, 2022(R-3 week)
14:09:40 <lajoskatona> That is next Thursday
14:10:03 <lajoskatona> I hope there will be no big issues with it :-)
14:10:24 <lajoskatona> if there is no comments for Yoga release we can move on
14:11:19 <lajoskatona> #topic Bugs
14:11:32 <lajoskatona> Report from lajoskatona: http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027445.html
14:11:52 <lajoskatona> I have 2 bugs to highlight here as they have no owner:
14:12:04 <lajoskatona> Duplicate IP address on LSPs in the same LS lead to unpredictable flow output (#link https://bugs.launchpad.net/neutron/+bug/1961046 )
14:12:49 <lajoskatona> this one is originally reported for OVN, but fnordahl set Neutron also affected
14:13:56 <lajoskatona> The other one:
14:14:01 <lajoskatona> [ovn-octavia-provider] OVN NB DB timeouts (#link https://bugs.launchpad.net/neutron/+bug/1961874 )
14:15:21 <lajoskatona> it's perhaps some "which package to use in my deployment" question, so perhaps nothing to do in our side
14:16:03 <lajoskatona> This week haleyb is the deputy, and next week it will be amotoki.
14:16:11 <amotoki> lajoskatona: regarding the first bug, a bug fnordahl referred still looks specific to ovn.
14:16:23 <amotoki> I am fine with my deputy turn
14:16:30 <lajoskatona> amotoki: thanks
14:17:20 <lajoskatona> amotoki: yes, but if I understand the comment it can be fixed from Neutron side, and perhaps that's quicker than to wait for OVN
14:17:52 <lajoskatona> "although the current OVN DB schema allows duplicates to occur it is the CMS's responsibility to avoid them."
14:18:21 <lajoskatona> this is the usual on which layer to fix something, and who will first fix it or wait till the other layer fix it :-)
14:19:51 <lajoskatona> ok if there is no more comments/question for bugs, we can move on
14:19:57 <amotoki> lajoskatona: yeah, fair enough
14:20:37 <opendevreview> Krzysztof Tomaszewski proposed openstack/neutron master: Don't set HA ports down while L2 agent restart.  https://review.opendev.org/c/openstack/neutron/+/826545
14:21:16 <lajoskatona> Outreachy
14:21:53 <lajoskatona> Last week we discussed some topics, and I quickly listed them ( I hope all):
14:21:55 <lajoskatona> https://wiki.openstack.org/wiki/Network/Meetings#Outreachy_ideas
14:24:01 <slaweq> lajoskatona: do You want me to add to that list the RFEs which I found last week and sent to You already?
14:24:03 <lajoskatona> slaweq: sent a few RFEs which should be ok
14:24:09 <slaweq> :)
14:24:13 <lajoskatona> thank, I just found the list
14:24:23 <lajoskatona> but please
14:25:44 <slaweq> ok
14:25:47 <slaweq> I will add them right now
14:26:22 <lajoskatona> Personally I like this one: #link https://bugs.launchpad.net/neutron/+bug/1870319 :[RFE] Network cascade deletion API call
14:26:25 <amotoki> it would be nice if we can show candidates we have to outreachy folks. slaweq's list is really nice and at a quick look there are candidates for the program.
14:26:51 <amotoki> "candidates" I mean are potential areas they can work on.
14:27:36 <slaweq> lajoskatona: yes, that's something what is useful for others (Kuryr), shouldn't be hard to implement but also may let someone to learn a lot IMO
14:27:44 <opendevreview> Krzysztof Tomaszewski proposed openstack/neutron master: Don't set HA ports down while L3 agent restart.  https://review.opendev.org/c/openstack/neutron/+/826545
14:27:56 <bcafarel> it is also useful for lazy developers :)
14:28:44 <lajoskatona> bcafarel: :-)
14:30:59 <slaweq> also https://bugs.launchpad.net/neutron/+bug/1892200 could be very useful IMO
14:32:40 <lajoskatona> I still have fears that 3 month for a student is short for such RFE :-)
14:33:06 <slaweq> You mean https://bugs.launchpad.net/neutron/+bug/1892200 ?
14:33:10 <lajoskatona> but perhaps I underestimate them (I try to remember how useless I was when I was student :P)
14:33:43 <slaweq> IMO this one should be pretty quick to do, it should be one or 2 patches most likely
14:33:46 <lajoskatona> yes or the other one for Net cascade deletion
14:33:49 <slaweq> only on the L3 agent's side
14:34:00 <slaweq> net cascade deletion may be longer, that's true
14:34:43 <lajoskatona> yes but imagine it for somebody who perhaps first works with a cloud
14:35:27 <lajoskatona> but on the other hand we have a saying like the "palm tree grows better if it is loaded" (soory I even can't recall the correct Hungarian version of it)
14:36:29 <slaweq> maybe I misunderstand something there but shouldn't we except that participants in this program will have some knowledge about it (at least basic)?
14:36:39 <mlavalle> IMO the tasks should be doable but also represent a stretch
14:36:50 <slaweq> and that keepalived config template rfe isn't really nothing very "cloud specific"
14:37:05 <slaweq> it's about generating config file based on the jinja2 template
14:37:10 <slaweq> nothing more really
14:37:14 <lajoskatona> slaweq: true
14:37:31 <mlavalle> yeah, in that sense, the net cascade delete is more reflective of cloud knowledge
14:37:47 <slaweq> net cascade deletion is more complicated as this involves api, knowledge about resources like port, subnet, etc
14:37:52 <mlavalle> which is what the community is promising the interns
14:38:23 <mlavalle> yeah, but I think that is really meaningful for a student who wants to learn really about cloud
14:38:45 <slaweq> mlavalle: I know, that's why I added it to the list :)
14:39:08 <elvira> This might be obvious, but I think the best way would be dividing the task if possible in 2 or 3 subtasks so that the student sees it as bit sized doable tasks instead of "wow I need to add a whole new feature, I don't know where to start" :)
14:39:13 <mlavalle> even if at the end, he / she doesn't conclude the entire RFE, it will provide very good knwledge along the way
14:39:37 <mlavalle> agree with elvira
14:39:53 <slaweq> elvira++
14:40:24 <lajoskatona> +1
14:40:39 <slaweq> but I think someone who will be mentor in that program can think about splitting RFEs into smaller tasks later
14:40:52 <elvira> slaweq: you are right!
14:41:29 <slaweq> btw. lajoskatona do we need to propose this week specific RFE(s) which we want assign to someone from outreachy program?
14:41:30 <lajoskatona> for that the 1st task is to review the spec, and perhaps the splitting can be written into it
14:41:38 <slaweq> and mentors for that/those rfes?
14:41:44 <slaweq> or how it works exactly?
14:42:44 <lajoskatona> this Friday the deadline for propsing project, here: https://www.outreachy.org/communities/cfp/openstack/
14:46:12 <mlavalle> I'd say propose net cascade deletion as is, and do the splitting later
14:46:19 <lajoskatona> anything can be  proposed whic is a meaningful project that can be assigned to an intern, and osmeody will mentor it
14:46:20 <slaweq> by project You mean "neutron" or specific rfe/thing to work on?
14:47:13 <lajoskatona> a project for outreachy is more a task, so not such general thing like Neutron as openstack project
14:47:29 <slaweq> ok
14:47:33 <mlavalle> that's what I think
14:47:38 <slaweq> so, personally I would go with this net cascade deletion too probably
14:48:00 <mlavalle> and an RFE is a concrete enough task that serves this purpose well
14:48:16 <slaweq> it gives some view about how cloud works, but isn't very related to the networking backend, it's like web application -rest api, db operations etc.
14:48:19 <lajoskatona> right, that's true it requires more learning
14:48:50 <lajoskatona> good option to learn rest API, and net concepts in Openstack
14:49:04 <lajoskatona> ok, let's go with it
14:49:24 <amotoki> it is true, but it is a good chance to understnad how the rest API handles resources :-)
14:49:27 <lajoskatona> This is the spec for it: https://review.opendev.org/c/openstack/neutron-specs/+/810822
14:50:23 <slaweq> it will require updates for sure
14:50:53 <mlavalle> yeah, but I think that to meet this week's deadline we have enough
14:51:41 <lajoskatona> I will propose it than
14:52:03 <lajoskatona> and later we can split it to smaller parts
14:52:08 <mlavalle> if nobody else does it, I will update the spec and try to come up with subtasks
14:52:38 <lajoskatona> mlavalle: thanks
14:53:00 <mlavalle> lajoskatona: do you know when the intern will start working with us?
14:53:19 <mlavalle> I want to have an idea of the deadline I have for this
14:53:48 <slaweq> mlavalle: https://www.outreachy.org/apply/project-selection/#openstack
14:53:51 <lajoskatona> mlavalle: no, but I can ask
14:53:55 <slaweq> there is some timeline
14:55:20 <lajoskatona> From May 30, 2022 to Aug. 26, 2022 ?
14:55:32 <mlavalle> yes, it looks like
14:56:05 <mlavalle> plenty of time to scrub the spec and reshape it in bite size bits
14:56:23 <slaweq> ++
14:56:30 <lajoskatona> mlavalle, slaweq, elvira: if I understand well you can help with it to participate in mentoring? I can also do mentoring
14:56:52 <opendevreview> Merged openstack/neutron master: Fix typo in the third instruction paragraph of "Controller nodes" block  https://review.opendev.org/c/openstack/neutron/+/831365
14:56:53 <elvira> I think usually the intern will try to contribute with low hanging fruit commit before May 30
14:57:00 <mlavalle> lajoskatona: yes, I'll be glad to work on the mentoring, either on my own or with elvira / slaweq
14:57:15 <slaweq> I can of course help if needed :)
14:57:24 <lajoskatona> ok, thanks
14:57:27 <elvira> sure thing lajoskatona, mlavalle. Please if you need any help ping me at any time, I'll be glad :)
14:57:48 <elvira> Or co-mentoring
14:57:54 <lajoskatona> I propose this rfe as project than, and we will see if we will have somebody who is interested :-)
14:58:11 <lajoskatona> ok, thanks everybody :-)
14:58:57 <lajoskatona> the time is up, if there's nothing more to discuss, we can close the meeting
14:59:20 <mlavalle> o/
14:59:42 <lajoskatona> o/
14:59:43 <slaweq> o/
14:59:43 <ralonsoh> bye
14:59:48 <lajoskatona> #endmeeting