14:00:01 #startmeeting neutron_drivers 14:00:01 Meeting started Fri Sep 29 14:00:01 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:01 The meeting name has been set to 'neutron_drivers' 14:00:05 hello 14:00:08 o/ 14:00:18 hi, sorry, can't participate today 14:00:25 np 14:01:18 o/ 14:01:41 ok, we are 4 core drivers here 14:01:45 lajoskatona, will join later 14:01:54 let's start with the agenda 14:02:06 first topic 14:02:11 Liu Xie liushy): [fwaas][rfe] support list type of port_range for firewall rule (I can't find this in the meeting logs) 14:02:16 #link https://bugs.launchpad.net/neutron/+bug/2028660 14:02:56 is Liu Xie here? 14:03:49 ok, are you willing to propose this RFE? sorry but I don't have the background for it 14:04:03 Merged openstack/neutron stable/2023.1: [OVN] Match LSP_TYPE_VIRTUAL in PortBindingUpdateVirtualPortsEvent https://review.opendev.org/c/openstack/neutron/+/896804 14:04:07 Merged openstack/neutron stable/zed: [OVN] Match LSP_TYPE_VIRTUAL in PortBindingUpdateVirtualPortsEvent https://review.opendev.org/c/openstack/neutron/+/896805 14:04:12 o/ 14:04:54 ok, I'll update the launchpad bug to request the author of this RFE to propose it during this meeting, next week 14:05:08 I suppose liushy is from pacific, so perhaps we have to warn that there will be a discussion 14:05:25 I should have sone it but this week was a little busy, I can send him/her a mail 14:05:33 lajoskatona, ok, I'll update the LP with the time and dates 14:05:40 and I'll ask him for feedback 14:05:50 cool 14:05:51 or we can discuss based on what we know based on the LP and ask questions teher 14:06:05 there 14:06:08 wait a sec with this RFE 14:06:15 mlavalle, ok, but as I said I have no background for this 14:06:17 I'm checking now our api-ref https://docs.openstack.org/api-ref/network/v2/index.html?expanded=create-firewall-rule-detail#fwaas-v2-0-current-fwaas-firewall-groups-firewall-policies-firewall-rules 14:06:23 so if anyone is willing to do it, perfect 14:06:29 and it says: "The source port or port range for the firewall rule. A valid value is a port number, as an integer, or a port range, in the format of a : separated range. For a port range, include both ends of the range. For example, 80:90." 14:06:38 isn't it what this rfe was proposing? 14:06:49 yes, it looks like it 14:07:10 even cooler, it is already finished than :-) 14:07:21 it seems so 14:07:23 then maybe is a bug 14:07:28 but I don't know about implementation 14:07:37 it's expecting list "source_port": ["22","23","30:80"] 14:07:59 but instead of list You can create couple of rules 14:08:12 so I'm not sure if it's good idea to do list there 14:08:17 we can add a comment to the LP pointing this out to submitter and ask what is being observed in the implementation 14:08:26 mlavalle++ 14:08:42 +1 14:08:53 +1 14:09:32 ok, I'll update the LP with the comments made here 14:09:48 so, if I'm not wrong, the suggestion is to create several rules 14:09:51 right? 14:10:02 in any case, it doesn't seem to warrant a new API or RFE. It seems more like a bug where the implementation doesn't meet what the API specifies 14:10:22 mlavalle, the API does not accept any list, accepts a single value or a range 14:10:29 so the API now is correct 14:10:39 ok 14:11:14 ok, I'll update the LP with your suggestions and, of course, if Liu wants to improve the API, he can propose it 14:11:14 then let's explore whether the current API can satisfy the expressed need 14:11:48 but I'm not going to approve yet the LP until we have some feeback from the author 14:11:55 yeap 14:12:03 that's exactly what we are saying 14:12:23 ok, any other comment? 14:12:47 perfect, thanks! 14:12:49 next one 14:12:58 lucasagomes, [OVN] Allow scheduling external ports on non-gateway nodes 14:13:03 #link https://bugs.launchpad.net/neutron/+bug/2037294 14:13:06 lucasagomes, please 14:14:00 ok, let me introduce this RFE 14:14:22 right now the OVN L3 scheduler can schedule the GW ports only on those marked as GW chassis 14:14:29 that is an option in "ovn-cms-options" 14:14:42 there are now no exceptions to this 14:15:06 however, OpenShift would require to schedule these GW ports on non-GW nodes 14:15:24 so a new config option, defining these chassis, is proposed 14:15:35 and of course the OVN L3 scheduler should be aware of this 14:16:12 IMO this is a RFE, because of the impact in the L3 scheduler 14:16:41 what I don't know, and I would like to discuss in advance (maybe in a spec or a patch) is how to implement that in the L3 scheduler 14:16:51 1) new scheduler or 2) modify the existing ones 14:17:27 Originally I thought a lightweiht RFE, but as you speak about it perhaps a spec would be good for it 14:17:59 I would prefer first to discuss in a small spec what changes are going to be made 14:18:12 +1, thanks for it 14:18:17 there are currently too many ongoing changes in the L3 scheduler 14:18:19 and also get a litle more detail on the use case 14:19:21 any other opinion? 14:19:40 small spec sounds good for me 14:19:46 +1 14:20:08 +1 14:20:11 +1 14:20:23 perfect then, I'll update the LP bug with this info 14:20:43 I have nothing else in the agenda, do you want to add something? 14:21:09 just that next Friday I won't attend the meeting, because I'll be off on PTO \o/ 14:21:15 enjoy 14:21:40 thank you very much for attending, this is most probably my last drivers meeting as chair. Have a nice weekend! 14:21:52 o/ 14:21:56 #endmeeting