14:00:09 <lajoskatona1> #startmeeting networking
14:00:09 <opendevmeet> Meeting started Tue Nov  2 14:00:09 2021 UTC and is due to finish in 60 minutes.  The chair is lajoskatona1. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:09 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:09 <opendevmeet> The meeting name has been set to 'networking'
14:00:16 <mlavalle> o/
14:00:23 <lajoskatona1> o/
14:00:24 <ralonsoh> hi
14:00:27 <isabek> Hi!
14:00:33 <obondarev_> hi
14:00:41 <haleyb> o/
14:00:49 <slaweq> hi
14:01:34 <lajoskatona1> I think we can start
14:01:56 <lajoskatona1> You can check the agenda here: https://wiki.openstack.org/wiki/Network/Meetings
14:02:08 <lajoskatona1> #topic Announcements
14:02:12 <rubasov> o/
14:02:36 <lajoskatona1> Yoga cycle calendar https://releases.openstack.org/yoga/schedule.html
14:03:12 <lajoskatona1> in 2 weeks we reach yoga-1 milestone
14:03:36 <dmitriis> o/
14:04:19 <lajoskatona1> Any announcements which we can discuss?
14:04:53 <lajoskatona1> ok, let's move on
14:04:56 <lajoskatona1> #topic Bugs
14:05:07 <lajoskatona1> obondarev was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025624.html
14:05:46 <lajoskatona1> obondarev: do you have anything to highlight?
14:06:05 <obondarev_> not really, all details are in the report I think
14:06:09 <lajoskatona1> I listed the bugs without owner to https://wiki.openstack.org/wiki/Network/Meetings
14:08:11 <lajoskatona1> Ok, Do you have any bug to discuss here?
14:09:37 <lajoskatona1> Personally I have the feeling that some from the list could be an RFE, like https://bugs.launchpad.net/neutron/+bug/1948891 ([ovn] Using ovsdb-client for MAC_Binding could theoretically block indefinitely) or https://bugs.launchpad.net/neutron/+bug/1949202 (ovn-controllers are listed as agents but cannot be disabled )
14:09:55 <lajoskatona1> or more a support request at current  state like https://bugs.launchpad.net/neutron/+bug/1949097
14:10:18 <slaweq> that last one I think can be closed IMO
14:10:43 <lajoskatona1> this one was discussed on  #neutron channel today, no?
14:10:45 <slaweq> we discussed it with ralonsoh and EugenMayer last week and today
14:10:56 <ralonsoh> yes, it is already solved
14:11:13 <slaweq> https://bugs.launchpad.net/neutron/+bug/1949059 this one worries me
14:11:22 <slaweq> I will try to take a look at it this week
14:11:50 <slaweq> but I'm not ovn-octavia-provider expert so it will for sure take me some time to catch up with it :)
14:12:36 <slaweq> regarding https://bugs.launchpad.net/neutron/+bug/1949202 - I have a question
14:12:46 <slaweq> is it really possible to disable e.g. neutron-ovs-agent?
14:12:52 <lajoskatona1> yeah this comment is hard: https://bugs.launchpad.net/neutron/+bug/1949059/comments/1
14:13:57 <ralonsoh> I can try to ping redhat folks about OVN octavia bug
14:14:46 <lajoskatona1> slaweq: the admin_state_up can be updated to true, but not sure what that really do in the background
14:14:54 <lajoskatona1> I mean false
14:15:22 <slaweq> exactly that's why I asked because I'm not sure if that has any real effect
14:15:55 <slaweq> I know that for dhcp/L3 agent it will not schedule networks/routers to such agents but for L2 agent I don't think it really do anything
14:16:26 <ralonsoh> I'll check it
14:16:40 <ralonsoh> if that affects the agent, we should do the same for OVN agents
14:16:47 <ralonsoh> if not, I'll document it in the bug
14:17:17 <slaweq> thx ralonsoh :)
14:18:49 <lajoskatona1> As I see no port will be scheduled to the agent if admin state is false
14:19:26 <slaweq> lajoskatona1: You mean ports will not be bound to the host where ovs-agent is disabled?
14:20:28 <lajoskatona1> yes, exactly: https://opendev.org/openstack/neutron/src/branch/master/neutron/plugins/ml2/drivers/mech_agent.py#L182
14:21:07 <slaweq> ok, so we should probably to the same for ovn-controller "agents"
14:21:35 <ralonsoh> I don't know if we can replicate this behaviour in those agents
14:21:52 <ralonsoh> but I'll check it
14:22:19 <lajoskatona1> yes, and perhaps check how other l2 agents work and try to "standardize" it and/or document what we have now
14:22:29 <ralonsoh> sure
14:22:32 <lajoskatona1> thanks ralonsoh
14:22:37 <slaweq> ++
14:23:05 <lajoskatona1> I check if this is something common for all l2 agents and if we have documentation for it
14:23:51 <lajoskatona1> ok, if nothing more for bugs......
14:23:57 <lajoskatona1> This week bcafarel is the deputy, and next week slaweq will be.
14:24:11 <lajoskatona1> Is that ok for you?
14:24:16 <slaweq> sure
14:24:24 <lajoskatona1> ok, thanks
14:24:30 <lajoskatona1> #topic L3 subteam
14:25:01 <lajoskatona1> To tell the truth I forgot to ping Liu the day before.....
14:25:38 <mlavalle> LOL
14:25:38 <lajoskatona1> ping liuyulong
14:26:41 <dasp_> Sorry, on the topic of bugs, I have interest in https://bugs.launchpad.net/neutron/+bug/1670666 (and resurrecting https://review.opendev.org/c/openstack/neutron/+/708011). Can I get some comments if that solution is still okay today or what to change?
14:26:45 <lajoskatona1> mlavalle: due to timezone (and perhaps irc availability) constraints sending a mail seems to be working :-)
14:28:52 <opendevreview> Merged openstack/neutron-specs master: Neutron VLAN networks with QinQ enabled  https://review.opendev.org/c/openstack/neutron-specs/+/798704
14:30:09 <lajoskatona1> dasp_: if I understand from last comments there was no general issue with it, so restore it and we can contiune the review after the things fixed in last comments
14:31:19 <slaweq> dasp_: I abandoned it automatically some time ago, but feel free to restore that patch and work on it
14:31:33 <slaweq> if You can't restore it in gerrit, I can do it for You
14:32:06 <dasp_> I don't think I can
14:32:31 <slaweq> It's restored now :)
14:33:18 <dasp_> thanks! I'll see what I can do.
14:33:25 <lajoskatona1> I think we can skip l3 section as there's no topics for it
14:33:48 <lajoskatona1> #topic ryu and os-ken
14:34:05 <ralonsoh> no updates from "parent" project, ryu
14:34:11 <ralonsoh> three patches to review
14:34:15 <ralonsoh> https://review.opendev.org/c/openstack/os-ken/+/815784
14:34:15 <lajoskatona1> https://review.opendev.org/q/project:openstack%252Fos-ken+status:open
14:34:23 <lajoskatona1> thanks ralonsoh
14:34:39 <ralonsoh> that's all today
14:34:56 <slaweq> tonight I will rebase my patches there to resolve conflicts
14:35:13 <slaweq> and when all will be merged I think we can do new os-ken release
14:35:15 <slaweq> wdyt?
14:35:21 <ralonsoh> sure thanks
14:35:27 <ralonsoh> check https://review.opendev.org/c/openstack/os-ken/+/815601
14:35:53 <lajoskatona1> slaweq: +1
14:37:53 <lajoskatona1> ralonsoh: eventlet 0.26.1 is what we use in Neutron for example?
14:38:04 <ralonsoh> let ne check
14:38:16 <ralonsoh> 0.25.1
14:38:20 <lajoskatona1> yeah we have eventlet>=0.25.1
14:38:30 <ralonsoh> but we install the last one
14:38:42 <ralonsoh> 0.32.0
14:39:32 <lajoskatona1> ralonsoh: ok
14:40:22 <lajoskatona1> If noting more for ryu/os-ken we can move on
14:40:50 <lajoskatona1> #topic On Demand Agenda
14:41:16 <lajoskatona1> Do you have anything in mind to discuss?
14:42:05 <slaweq> just a short reminder if someone missed my email - today's CI meeting will be a video meeting
14:42:14 <slaweq> if someone is interested, please join :)
14:42:25 <slaweq> it will be in 18 minutes (after that one)
14:42:38 <dmitriis> https://blueprints.launchpad.net/neutron/+spec/off-path-smartnic-dpu-port-binding-with-ovn
14:43:10 <slaweq> ahh, and also, I prepared doodle https://doodle.com/poll/3n2im4ebyxhs45ne?utm_source=poll&utm_medium=link to choose the best time slot for ci meeting
14:43:12 <dmitriis> Looking for reviews on this spec https://review.opendev.org/c/openstack/neutron-specs/+/788821
14:43:49 <lajoskatona1> slaweq: cool
14:45:39 <lajoskatona1> dmitriis: there's a nova spec for it as well: https://review.opendev.org/c/openstack/nova-specs/+/787458
14:45:43 <dmitriis> If anybody has bandwidth, it would be much appreciated. At the Nova side, this spec https://review.opendev.org/c/openstack/nova-specs/+/787458 was gated on the approval of the Neutron spec by the core devs.
14:46:15 <frickler> another review on https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/815294 would also be nice
14:46:36 <dmitriis> lajoskatona1: yes, here is the pointer to Nova cores wanting a review from Neutron first https://etherpad.opendev.org/p/nova-yoga-ptg#L561
14:47:04 <lajoskatona1> dmitriis: ok, thanks, I will check it
14:47:07 <dmitriis> as such, the Nova spec have went through several iterations ~April - May 2021
14:47:26 <lajoskatona1> frickler: I will check it
14:47:29 <dmitriis> so, there isn't much left to agree on there from what I can tell, just trying to get ordering right
14:47:34 <dmitriis> lajoskatona1: tyvm
14:48:52 <lajoskatona1> dmitriis: np
14:49:34 <lajoskatona1> ok, if nothing more for today's meeting we can close here and prepare for the video CI meeting :-)
14:49:50 <dmitriis> lajoskatona1: feel free to ping me or fnordahl if any questions arise. There is a WIP review for it already which may make it easier to see what's in it for Neutron https://review.opendev.org/c/openstack/neutron/+/808961 (likewise, there is code for Nova here https://review.opendev.org/c/openstack/nova/+/812111/)
14:50:22 <lajoskatona1> dmitriis: ack, I saw the link to the patch as comment :-)
14:50:39 <lajoskatona1> #endmeeting