14:00:21 <lajoskatona> #startmeeting networking
14:00:21 <opendevmeet> Meeting started Tue Jul 12 14:00:21 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:21 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:21 <opendevmeet> The meeting name has been set to 'networking'
14:00:22 <lajoskatona> o/
14:00:49 <obondarev> hi
14:00:53 <elvira> o/
14:01:03 <mlavalle> o/
14:02:10 <rubasov> o/
14:02:17 <amotoki> o/
14:02:29 <ralonsoh> hi
14:03:22 <lajoskatona> Ok, let's start, thanks for coming to the meeting instead of the beach :-)
14:03:29 <lajoskatona> #topic Announcements
14:03:39 <lajoskatona> The usual Zed schedule: https://releases.openstack.org/zed/schedule.html
14:03:58 <lajoskatona> We received the usual Release countdown for week R-12, Jul 11 - 15: (#link https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029465.html)
14:04:13 <lajoskatona> What is interesting for us:
14:04:17 <lajoskatona> lib releases
14:04:49 <lajoskatona> as I saw yesterday we can have a new n-lib release, we have few new patches  merged, and perhaps for ovsdbapp also
14:06:14 <lajoskatona> the other one is for the coming week:
14:06:20 <lajoskatona> Zed-related specs should now be finalized so that teams can move to implementation ASAP
14:06:34 <lajoskatona> so we should check the hanging specs
14:07:51 <lajoskatona> Do you have any comments/questions for the above topics?
14:08:17 <bcafarel> late o/ (no I was not on the beach)
14:08:28 <lajoskatona> bcafarel: Hi
14:08:42 <lajoskatona> ok
14:08:57 <lajoskatona> I have a small half announcement for the PTG
14:09:04 <lajoskatona> I registered the team for it
14:09:28 <lajoskatona> and actually I started to ask around if there will be some solution for hybrid participation
14:09:44 <lajoskatona> to have possiblity to connect remotely
14:10:25 <lajoskatona> we have cores who most probably can't travel to the US and perhaps others would also join in if they can't travel
14:10:28 <bcafarel> may be quite useful for some, +1
14:10:32 <lajoskatona> what do you think?
14:10:44 <ralonsoh> +1 from me
14:10:51 <obondarev> +1
14:11:29 <amotoki> +1
14:11:56 <lajoskatona> and actually as a special guest I asked svinota from pyroute2 (aka Peter Saveliev) if he would join us for a session to have a common discussion what he and we plan for the next months
14:12:40 <lajoskatona> and he is really happy to join us, so we can collect pyroute2 related questions or issues, or perhaps even ask him to give some background for pyroute2
14:13:30 <ralonsoh> that would be great
14:13:46 <mlavalle> +1
14:14:33 <lajoskatona> I am not sure if he can travel, he said he need a sponsor for it, but if we have some proper video tool that can be ok for him also :-)
14:15:32 <lajoskatona> Ok, that's all for announcements from me, do you have any comments/questions for it?
14:16:01 <ralonsoh> no thanks
14:16:30 <lajoskatona> #topic Bugs
14:16:36 <lajoskatona> Report from lucasgomes: https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029494.html
14:17:00 <lajoskatona> as I saw all bugs has owner
14:17:43 <lajoskatona> This week jlibosva is the deputy and next week obondarev will be.
14:17:58 <jlibosva> o/ ack
14:18:03 <obondarev> o/
14:18:10 <lajoskatona> jlibosva, obondarev: thanks
14:18:29 <lajoskatona> If no questions/comments for bugs we can go on
14:19:12 <lajoskatona> #topic On Demand Agenda
14:19:21 <lajoskatona> (lajoskatona): Outreachy & Network cascade delete
14:19:42 <lajoskatona> skoech[m] is started to work on the feature
14:20:23 <skoech[m]> Hi, that's me.
14:20:29 <ralonsoh> links to the patches? (if any)
14:20:36 <skoech[m]> https://review.opendev.org/c/openstack/neutron-lib/+/849046
14:20:47 <skoech[m]> You can check out my WIP.
14:20:57 <ralonsoh> nope
14:21:02 <ralonsoh> only you can remove it
14:21:13 <skoech[m]> Any comments/help/advise is welcome.
14:21:18 <lajoskatona> the spec is here: https://review.opendev.org/c/openstack/neutron-specs/+/810822
14:21:26 <mlavalle> I think she means we cn look at the patches
14:21:47 <skoech[m]> mlavalle: yeah.
14:22:16 <mlavalle> skoech[m]: question. They are on merge conflict as of now? Are you going to fix that soon and then we look at the patches?
14:22:20 <skoech[m]> https://review.opendev.org/c/openstack/neutron/+/849039
14:22:21 <lajoskatona> Actually when slaweq is back I would like to ask him also to take a look as this was originally his spec, we just added to outreachy mentorship program
14:22:44 <lajoskatona> mlavalle: today we checked that and it seems like a gerrit bug, because they are on top of master
14:23:07 <mlavalle> lajoskatona: ack, I'll "check them out" then
14:23:13 <mlavalle> ;-)
14:23:18 <skoech[m]> mlavalle: yes, we are working on fixing the merge conflicts with lajoskatona and elvira .
14:24:01 <skoech[m]> s/advise/advice/
14:24:10 <lajoskatona> skoech[m]:  thanks, if you need help, just ping us on the chat :-)
14:24:21 <elvira> lajoskatona: I've been thinking and... could the duplicated issue trigger that merge conflict state somehow? although none of them are merged so it doesn't make much sense to me
14:24:27 <amotoki> skoech[m]: great. it would be nice if you mention the spec link in the commit msg
14:24:30 <skoech[m]> lajoskatona: will do, thanks.
14:25:08 <skoech[m]> amotoki: okay, thank you.
14:25:15 <lajoskatona> elvira: no idea, but possible
14:25:33 <amotoki> skoech[m]: thanks. it would really help reviewers understand the context :)
14:25:42 <mlavalle> and thank you for helping us with this skoech[m]. Your help is much apreciated and highly valuable
14:26:07 <skoech[m]> amotoki: :)
14:26:48 <skoech[m]> mlavalle: no, thank you. I'm happy to help in any way. I'm also learning a lot.
14:27:16 <skoech[m]> :)
14:27:29 <lajoskatona> ok, we can move on to the next topic:
14:27:33 <lajoskatona> (mlavalle): Next steps to merge https://review.opendev.org/c/openstack/neutron/+/837780
14:28:04 <mlavalle> this is one of the topics we decided in the PTG
14:28:25 <mlavalle> the corresponding os-vif patch is long merged
14:28:46 <mlavalle> so, what do we need to do to move ahead with the Neutron patch?
14:29:05 <ralonsoh> os-vif is a Nova library
14:29:11 <ralonsoh> that will be for sure in Z+1
14:29:18 <ralonsoh> but we can't ensure that for Z
14:29:30 <ralonsoh> in those cases we create a config knob to enable this feature
14:29:36 <amotoki> mlavalle: do we have a os-vif release including your chnage?
14:30:00 <mlavalle> I don't know, if that's what we need, I'll track it down
14:30:26 <lajoskatona> yeah, I suppose there will be an os-vif reelase recently
14:31:22 <lajoskatona> but I don't understand what ralonsoh said, we have to wait for Z+1 for merging this if we need a new os-vif release?
14:31:28 <ralonsoh> no
14:31:36 <ralonsoh> this is used by Nova
14:31:45 <ralonsoh> when we need to sync with other project, in this case nova
14:31:58 <ralonsoh> what we usually create is a config knob to enable/disable this improvement
14:32:02 <lajoskatona> ahh ok, we have to wait tille we have os-vif release and nova starts consuming it?
14:32:08 <ralonsoh> exactly
14:32:17 <ralonsoh> because we can't enforce this from neutron
14:32:37 <lajoskatona> ok, it's more clear now
14:32:45 <mlavalle> and the config knob would be in Neutron with a default value of disabled?
14:32:51 <ralonsoh> yes
14:33:10 <ralonsoh> that's the pain of syncing with other projects
14:33:14 <mlavalle> ok, I'll create that config option
14:33:32 <mlavalle> I'm goin to do it in the same patch
14:33:35 <amotoki> do we really need a config option?
14:33:49 <ralonsoh> this way you can enable it in Z
14:34:10 <ralonsoh> manually checking first Nova is consuming the required os-vif version
14:34:16 <lajoskatona> as I see there is no proposed patch to have new os-vif release
14:34:36 <ralonsoh> no because there is no releases proposal for os-vif yet
14:34:41 <amotoki> as long as a new os-vif is backward-compat for other features I am not sure we really need a config option but a config option would be safer
14:34:42 <ralonsoh> but we can push it now
14:35:07 <ralonsoh> amotoki, os-vif is backward compatible
14:35:14 <amotoki> ralonsoh: yeah
14:35:16 <ralonsoh> but older versions wont' have the improvement required
14:35:42 <ralonsoh> this is why, in Z, an admin should enable the Neutron config knob manually, after checkign the nova os-vif version
14:37:45 <obondarev_> +1 makes sense to me
14:38:00 <lajoskatona> +1, agree, let's go the safe way
14:38:13 <mlavalle> +1
14:38:16 <amotoki> sounds good
14:38:28 <mlavalle> that's all I needed for today
14:38:47 <lajoskatona> mlavalle: thanks, for bringing it here, and pushing it forward
14:39:21 <lajoskatona> If there is no more topics you would like to discuss we can close the meeting for today
14:40:25 <lajoskatona> #endmeeting