14:01:49 #startmeeting neutron_drivers 14:01:49 Meeting started Fri Jan 14 14:01: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:01:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:49 The meeting name has been set to 'neutron_drivers' 14:01:51 thx frickler 14:01:53 o/ 14:01:56 o/ 14:01:58 hi 14:01:58 o/ 14:02:39 hi 14:03:04 hi 14:03:04 Ok so our topic for today is: Can neutron-fwaas project be revived? 14:03:11 see the thread: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026413.html 14:03:53 it was Inspur who would like to use and maintain fwaas 14:04:36 I hope they can join 14:05:23 hi 14:05:31 Actually I am fine with opening fwaas again and have it as Neutron stadium 14:05:41 do you know what functionality from fwaas was needed? 14:05:44 just asking 14:05:52 what I miss in context that what fwaas can offer that is not covered with security-groups? 14:06:08 L3 FW 14:06:17 ralonsoh: thanks 14:06:17 on router ports, for example 14:06:31 +1 14:06:57 I'm personally not against reviving it but I would vote for doing it in the x/ namespace, at least for now 14:07:10 right, ok with this 14:07:19 slaweq: ok 14:07:23 if problem will be really maintained, we can thing about moving it to the stadium some day, but not now 14:07:30 that's my opinion about it 14:07:48 We have many customers who want to set simple rules through the security group. Layer 3 sets complex rules through the firewall 14:08:20 zhouhenglc: hi, so you need L3 firewall ? 14:08:34 We have implemented firewall based on ovn 14:08:34 Logical_Router_Policy 14:08:48 lajoskatona: yes 14:09:09 zhouhenglc: so You have Your own implementation of the fwaas, right? 14:09:43 do You want to maintain only that new, ovn based implementation or the original one which was in fwaas too? 14:09:52 We are based on the original neutral-fwaas implementation 14:10:10 so you would manintain both, then, correct? 14:10:25 the entire thing I mean 14:10:48 yes both 14:11:51 if we vote to have it now under x/ you have to start to renaming process 14:12:14 I can help in that, I have to fetch my old memories 14:12:23 lajoskatona: renaming does not happen. a new repo named as x/neutron-fwaas should be created. 14:13:01 amotoki: yes that is true 14:13:01 it can be created from openstack/neutron-fwaas, so the new x/ repo can have the whole history. 14:13:24 yes it happened with networking-l2gw 14:14:10 jpic proposed openstack/neutron stable/xena: WIP: allow multiple segments per host https://review.opendev.org/c/openstack/neutron/+/824718 14:14:11 as I remember to x/ direction is simpler don't need to wait for gerrit restart, but that is not that iteresting now, sorry,.... 14:15:11 zhouhenglc: what do you say, is that ok for you to have fwaas revived under x/ namespace, and we can later see to move it back to openstack/neutron-fwaas? 14:16:11 lajoskatona: I think it's good, too. 14:16:33 zhouhenglc: ok, cool 14:17:11 shall we vote on then to revive neutron-fwaas under x/ namespace? 14:17:16 yeap 14:17:19 +1 from me 14:17:20 +1 from me 14:17:22 +1 14:17:29 +1 14:17:30 +1 from me 14:17:58 +1 14:18:21 ok, we have the result, thanks :-) 14:18:39 I only contributed to the neutron project before. What do I need to do about neutron-fwass now 14:19:01 nothing else, same as for Neutron 14:19:51 zhouhenglc: to start the moving/renaming process a patch is necessary and TC will dicsuss it on next TC meeting 14:20:10 I have to check the name of the repo and the format 14:20:13 zhouhenglc: to be clear... in the ml thread I suggested you and your team start creating a document similar to https://review.opendev.org/c/openstack/neutron-specs/+/506012. If you are happy with the x/ namespace and plan to remain there, that document is not necessary. It would be necessary only if in the future you want to bring fwaas to the Neutron stadium 14:20:57 I don't want you to spend cycles on something that might not be necessary 14:21:08 mlavalle: thanks 14:21:23 lajoskatona: to be clear I think no TC discussion is required as x/ namespace is not controlled by TC. 14:21:31 The repo is openstack/governance 14:21:45 ok perhaps it is only necessary for the other direction... 14:22:04 it is just required when opentack/neutron-fwaas repo will be retired completely including the stable branches. 14:24:18 ok, I think we can close the "official" part of the meeting, and I can ask infra what we need to revive fwaas under x/ 14:24:41 the next step is to prepare a new repo x/neutron-fwaas. 14:24:59 we can follow https://docs.opendev.org/opendev/infra-manual/latest/creators.html 14:25:45 amotoki: thanks, I was looking for this :-) 14:26:06 amotoki: "prepare a new repo x/neutron-fwaas" need me to do something? 14:26:34 zhouhenglc: you can. we can support you. 14:27:16 zhouhenglc: the above URL of the infra manual explains what you need to do. 14:28:10 amotoki: thanks, I learn the above 14:28:10 URL 14:29:27 ok, I think we can close than the meeting, thanks for the participation 14:29:29 If I may, I'd like to bring up https://bugs.launchpad.net/neutron/+bug/1905391 (RFE VPNaaS for OVN) 14:30:05 the work there is actually finished, I'd appreciate a review. If there's anything missing, please let me know 14:31:07 You mean this patch: https://review.opendev.org/c/openstack/neutron-vpnaas/+/765353 ? 14:31:26 yes 14:31:42 thanks for highlighting it, 14:32:39 ok, if there is no more things to discuss... 14:33:21 #endmeeting