14:01:13 #startmeeting networking 14:01:13 Meeting started Tue Jun 14 14:01:13 2022 UTC and is due to finish in 60 minutes. The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:13 The meeting name has been set to 'networking' 14:01:16 Hi 14:01:30 hi 14:01:33 hi 14:01:34 hi 14:01:35 o/ 14:01:52 hi 14:01:54 рш 14:01:56 o/ 14:01:56 hi 14:01:57 hi 14:02:52 #topic Announcements 14:03:04 the usual Zed schedule: https://releases.openstack.org/zed/schedule.html 14:03:38 And the last release announce mail from elodilles: [release] Release countdown for week R-17, Jun 06 - 10: http://lists.openstack.org/pipermail/openstack-discuss/2022-June/028817.html 14:04:03 What I see in it as important but not urgent: 14:04:08 "The Zed-2 milestone will happen in next month, on July 14th, 2022." 14:05:28 on the last meeting we discussed to EOL old branches: Q, R & S for stadiums 14:05:48 as there was no answer in the last 2 weeks, I will push patches to make this happen 14:06:03 lajoskatona++ 14:06:17 what about Neutron itself, do we want to do the same there or not yet? 14:07:02 for stadiums we have bad job configs and no backports 14:07:28 but for Neutron that is not true so I would say if we have some activity we can keep the branches 14:07:57 but I havent checked these branches for Neutron itself :-( 14:08:05 last patch for Queens was in March, so indeed we can wait a bit longer 14:09:04 slaweq: thanks 14:10:15 I added one more topic to the announcements: 14:10:21 Summit is over 14:10:31 Keynote videos are already out: 14:10:35 https://youtu.be/ZlPLGmBfaVc 14:10:40 https://youtu.be/Jpu7SPLvjjE 14:11:38 just a kind of personal suprise factor list, what was new for me (after ~2 years of home office): 14:12:21 governments are really interested in opensource (security on top prio) 14:12:45 Foundation tries to focus more on project teams: 14:13:09 mentoring for example in focus 14:13:23 and what i am really interested to see: 14:13:32 more statistics to help better collaboration with the help of bitergia 14:15:03 and of course it was really good to see folks again :-) 14:15:33 ++ 14:15:36 lajoskatona: +1, nice to meet many of you there :) 14:15:41 it was great to be there 14:15:47 +1 14:16:50 if no questions or notes for announcements we can move on 14:17:18 #topic Bugs 14:17:26 Report from haleyb: http://lists.openstack.org/pipermail/openstack-discuss/2022-June/028859.html 14:18:03 I saw a few without owner 14:18:11 The sync_routers interface takes too long (#link https://bugs.launchpad.net/neutron/+bug/1976345) 14:18:38 i thought there was a change proposed for that 14:18:46 cool, liuyulong started to work on this 14:18:57 haleyb: thanks, I see now 14:19:19 OVN: Metadata is not provisioned for a network with DHCP turned off (#link https://bugs.launchpad.net/neutron/+bug/1976366) 14:19:20 it still needs some work as the fix was re-introducing an old bug 14:20:15 haleyb: yes I see your comment, thanks for keeping an eye on it 14:22:18 this OVN one might be related to https://bugs.launchpad.net/neutron/+bug/1918914 14:22:47 But if there is no DHCP port, how does OVN provide metadata? i don't think it will 14:23:13 there is a metadata poert 14:23:23 OVN does not use the DHCP one 14:23:34 actually there is no DHCP port 14:24:32 there is this "distributed" port which is configured in ovn-meta namespace on each compute node where network is 14:25:30 this is the owner of this port 14:25:36 yeah 14:26:14 as commented by yatin, this is a duplicate (c#5) 14:26:36 https://bugs.launchpad.net/neutron/+bug/1918914/comments/5 14:27:14 yeah, let's wait till the reporter comes back if the solutions for https://bugs.launchpad.net/networking-ovn/+bug/1950180 are good for their case 14:27:20 in the bug it shows neutron:cidrs is "" so the OVN metadata doesn't get provisioned. In Ussuri was there a distributed port? 14:29:17 the user is expecting metadata to be served when dhcp disabled 14:29:29 as per other bug https://bugs.launchpad.net/neutron/+bug/1976366 14:30:04 is this some valid use case or they need to rely on config-drive for this case? 14:30:24 we can handle this offline 14:30:27 but please 14:30:38 don't mix the concepts: we reused the DHCP port as metadata 14:30:45 and then we renamed it after ussuri 14:30:49 but this is not a DHCP port 14:31:01 k sorry me not aware 14:31:22 ok, let's move on then 14:31:35 haleyb: is there any bug which we should mention here? 14:32:19 no i think that was it, there's also bugs from last week 14:32:30 haleyb: thanks 14:32:40 Report from amotoki: http://lists.openstack.org/pipermail/openstack-discuss/2022-June/029024.html 14:34:01 I see this one which can be interesting: https://bugs.launchpad.net/neutron/+bug/1978088 (After ovs-agent restart, table=21 and table=22 on br-tun openflow table is missing) 14:34:31 amotoki: do you have perhaps more that needs more attention or without owner? 14:35:01 no, this is the only one untriaged 14:35:12 amotoki: thanks 14:35:48 This week mlavalle is the deputy and next week rubasov will be. 14:35:56 #topic On Demand Agenda 14:35:59 ack 14:36:18 rubasov: thanks 14:36:44 Is there anything you would like to discuss? 14:36:51 yes, I have one thing 14:36:59 related to the OSC and neutron-vpnaas 14:37:27 during summit I talked with @gtema and he told me that they recently discovered that OSC don't have support for neutron-vpnaas 14:38:02 amotoki can it be that when we were checking what is still missing in OSC/SDK, vpnaas wasn't supported really and that's why we missed it there? 14:38:16 or maybe there was any different reason why it wasn't added to the SDK and OSC 14:38:17 neutorn-vpnaas is supported by neutronclient OSC plugin 14:38:26 it is true for all advanced services 14:38:48 ahh, ok so it should be in OSC by neutronclient python bindings 14:38:54 and we don't need that in SDK, right? 14:39:07 yes, at the moment 14:39:10 ok 14:39:21 but it might be a good chance to discuss the future of python bindings 14:39:30 I will talk about it with gtema 14:39:33 OSC neutron plugin now depends on python-neutronclient python bindings 14:40:09 and we deprecated that, no? 14:40:19 lajoskatona no 14:40:27 lajoskatona: I don't think we've deprecated the bindings 14:40:31 we deprecated and want to remove neutronlicent CLI 14:40:40 not python bindings (so far at least) 14:40:41 ok, true 14:40:52 we just discussed, I remember now 14:40:56 that was confusing me for long time too :) 14:41:23 yeah, really confusing 14:41:24 I remember that heat and other things also use bindings from neutronclient 14:41:49 so it is not just a documentation question :-) 14:43:07 yeah, I don't think we will be able to quickly get rid of it 14:43:13 but good that it's in OSC that way 14:43:13 this was discussed in yoga ptg https://etherpad.opendev.org/p/neutron-yoga-ptg#L372 14:43:28 I hope it will be fine for gtema and other OSC folks 14:43:44 thanks slaweq for bringing it here 14:43:48 isabek: thanks 14:44:09 lajoskatona yw, that's one of the follow ups after the summit :) 14:44:26 I will have some more but not this week, I need to check/prepare some stuff in next weeks 14:45:48 that's all from me, thx 14:45:57 thanks 14:45:59 if there is no more topics, we can close the meeting for today 14:46:11 please remember about CI meeting in 14 minutes 14:46:17 it's on video this week :) 14:46:58 slaweq: thanks, I wanted to ask which week we have :-) 14:47:16 yeah, it's the jitsii week :) 14:47:26 :-) 14:47:30 #endmeeting