15:00:46 #startmeeting neutron_qos 15:00:47 Meeting started Tue Mar 27 15:00:46 2018 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:50 The meeting name has been set to 'neutron_qos' 15:00:56 hi on another meeting :) 15:01:01 hi again 15:01:16 hi rubasov 15:01:34 mlavalle: will You attend? 15:01:40 o/ 15:01:48 of course 15:01:52 great 15:02:19 I don't think there will be anyone else here so we can start IMO 15:02:25 #topic RFEs 15:02:37 first rfe 15:02:40 #link https://bugs.launchpad.net/neutron/+bug/1596611 15:02:41 Launchpad bug 1596611 in neutron "[RFE] Create L3 floating IPs with qos (rate limit)" [Wishlist,Fix committed] - Assigned to LIU Yulong (dragon889) 15:02:56 I would like to announce that it's finally done 15:03:05 scenario tests are merged finally 15:03:05 \o/ 15:03:22 there is some issue with DVR but it will be treated as bug 15:03:46 so rfe and BP can be closed finally (if it isn't yet) 15:04:19 actually it is marked as "fix commited" so that's fine also 15:04:27 so, next rfe is #link https://bugs.launchpad.net/neutron/+bug/1727578 15:04:28 Launchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged] 15:05:10 there wasn't to much changes on this one recently but today zhaobo6 wrote there that he will continue work on this specs 15:05:25 specs is at https://review.openstack.org/#/c/531074/ 15:05:49 so I don't think that there is anything to add on this one today 15:06:21 next one on my list is #link https://bugs.launchpad.net/neutron/+bug/1560963 15:06:22 Launchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] 15:06:49 and TBH I didn't have any time to work on PoC for such backend implementation for minimum bandwidth 15:07:21 if there is someone else who would like to work on it - feel free to take it :) 15:07:53 I will try to email ralonsoh and ask for some details how he planned to do it in the past 15:07:57 when we say eggress... 15:08:28 who's point of view is that? 15:08:39 it's VM's point of view 15:08:57 so this is direction which is harder to implement 15:09:19 but it's the one which makes more sense from user's perspective 15:10:09 I'm a bit lost 15:10:16 rubasov: why? 15:10:21 isn't this completed for at least SR-IOV? 15:10:28 for SR-IOV yes 15:10:35 https://docs.openstack.org/neutron/latest/admin/config-qos.html 15:10:42 is the RFE for all drivers then? 15:10:44 but it isn't done for linuxbridge and for ovs 15:10:52 o/ 15:10:55 okay, got it, thanks 15:11:01 ahhh ok, that is what got rubasov and me confused 15:11:10 it was quite easy to do it for sr-iov 15:11:20 but it is much harder for other backends 15:11:43 as traffic which is egress from VM is in fact ingress from bridge perspective 15:11:51 yeap 15:12:00 and tc don't do shaping on ingress :/ 15:12:04 we cannot shape it 15:12:16 so we will probably need to play with ifb devices to achieve that 15:12:29 but I have no any experience with this 15:13:35 I guess time to experiment and learn 15:13:50 mlavalle: yes, excactly :) 15:14:03 so, moving on to the next one? 15:14:10 + 15:14:35 next one is #link https://bugs.launchpad.net/neutron/+bug/1578989 15:14:36 Launchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq) 15:14:51 and it is related to previous one :) 15:15:12 rubasov: You are working on it now, right? 15:15:20 I just uploaded a new patch set for the spec 15:15:39 yes, I saw it and will try to do review today or tomorrow morning 15:15:51 includes an idea how to use binding:profile 15:16:03 rubasov: did my comment about using binding:vnic_type and binding:profile make sense? 15:16:10 great 15:16:11 tomorrow I hope to look into how qos rule validation work 15:16:22 mlavalle: absolutely 15:16:30 rubasov: ping me if You will have any questions about this validation 15:16:45 I was doing it so I hope I will be able to help :) 15:16:51 I think the same will aplly to the spec on the nova side 15:17:15 we can simplify several things by comminicating with binding:profile 15:17:15 because I'm not yet satisfied with having two rules (one for data plane enforcement, one for placement enforcement) either 15:17:24 slaweq: will do, thanks 15:18:14 today I will try to provide feedback on the Nova side 15:18:17 mlavalle: yep, it simplifies for neutron, but it complicates for nova 15:18:37 and tomorrow I will try to come back to the Neutron one 15:18:41 mlavalle: because that information first has to go down to nova-compute (today it does not) 15:19:04 mlavalle: but I'm talking about that to gibi 15:19:13 ok 15:21:07 I want also to mention that lajoskatona_ did 2 patches related to this rfe for neutron-lib: https://review.openstack.org/#/c/554532/ and https://review.openstack.org/#/c/552938/ 15:21:18 please add it to Your list of reviews :) 15:21:43 I hope to catch up with Lajos's patches soon 15:21:50 rubasov: thx 15:22:03 Slaweq: I just on the way to refresh one of those 15:22:39 lajoskatona_: thx for info 15:22:56 Nice! 15:23:55 moving on to the next one 15:24:05 there is one postponed rfe: #link https://bugs.launchpad.net/neutron/+bug/1505627 15:24:06 Launchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Triaged] - Assigned to Reedip (reedip-banerjee) 15:24:47 I just wanted to mention that reedip told me recently that he should soon work on it again 15:25:51 if there are no questions about rfe we can go to next topic I think 15:25:53 since this is just enabling ECN autonegotiation as opposed to actually managing anything within ECN I think this should be not too difficult 15:26:17 njohnston: right, I think that this one should be easy to implement 15:28:02 ok, going on to next topic 15:28:04 #topic Bugs 15:28:23 there is one "fresh" bug #link https://bugs.launchpad.net/neutron/+bug/1758316 15:28:24 Launchpad bug 1758316 in neutron "Floating IP QoS don't work in DVR router" [High,Confirmed] - Assigned to LIU Yulong (dragon889) 15:28:40 it is related to FIP QoS and DVR 15:29:01 I found that it's not working fine in our dvr scenario job 15:29:28 so for now I added patch to skip this test if dvr is enabled: https://review.openstack.org/#/c/555747/ 15:29:49 and I hope that LIU Yulong will find out why it's not working properly 15:30:48 is he aware? 15:31:00 yes, he even wrote some comment there 15:31:04 ok 15:31:20 he is good following up 15:31:26 I will try to ask him about progress this week 15:31:53 any questions on this one? 15:32:28 not from me 15:32:47 nope 15:32:56 ok, I have also 2 old bugs on my list: 15:33:00 #link https://bugs.launchpad.net/neutron/+bug/1639186 15:33:01 Launchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] 15:33:07 and #link https://bugs.launchpad.net/neutron/+bug/1732852 15:33:09 Launchpad bug 1732852 in neutron "neutron don't support Router gateway rate limit " [Low,In progress] 15:33:30 with both of them still nothing changed since long time 15:34:14 speaking about #link https://bugs.launchpad.net/neutron/+bug/1732852 - I don't know if we can do anything with it 15:34:15 Launchpad bug 1732852 in neutron "neutron don't support Router gateway rate limit " [Low,In progress] 15:34:30 that can only work if veth will be used 15:34:56 but I don't know if we can do anything else except mention that constraint in docs 15:35:10 like was done some time ago: https://review.openstack.org/#/c/523153/ 15:36:05 I know that Ihar wanted to enforce using veth if rate limit is used but I'm not sure if that is good approach 15:36:15 mlavalle: what do You think about that? 15:37:18 don't know. let me look into it 15:37:29 I'll get back to you 15:37:53 mlavalle: sure, maybe You can just wrote a comment in this bug report if You will read it 15:38:03 I will do that 15:38:15 thx a lot mlavalle 15:38:28 and that was all on my bugs list for today 15:38:36 any questions? 15:38:43 something to add? 15:38:47 nope 15:38:54 pretty good update 15:39:00 thx 15:39:07 thanks for keeping track of all this 15:39:23 +1 really awesome job slaweq 15:39:32 so if anyone has anything to other to talk about I think we can finish earlier today :) 15:39:34 njohnston: thx :) 15:39:50 * slaweq will have few minutes before next meeting 15:40:00 thx for attending guys 15:40:09 and btw. happy easter to all of You 15:40:32 Same to you! 15:40:38 thx 15:40:42 #endmeeting