15:01:13 #startmeeting neutron_qos 15:01:14 Meeting started Tue Jan 30 15:01:13 2018 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:17 The meeting name has been set to 'neutron_qos' 15:01:21 hi everyone 15:01:30 we will wait few minutes for mlavalle to be back 15:01:48 Hi, 15:03:52 hi fouadben 15:05:15 * mlavalle is back 15:05:31 ok, so I think we can start now 15:05:37 welcome once again 15:05:45 #topic RFEs 15:06:22 there is still nothing new with #link https://bugs.launchpad.net/neutron/+bug/1560963 15:06:23 Launchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] 15:06:29 so I will not talk about this one 15:06:44 next one is also very old: #link https://bugs.launchpad.net/neutron/+bug/1578989 15:06:45 Launchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel) 15:07:17 here I only continue ralonsoh work on some placement client in neutron-lib: #link https://review.openstack.org/#/c/512396/ 15:07:40 but there is nothing else to add there still 15:07:52 slaweq: is it good to be revieiwed? 15:08:01 mlavalle: yes, please :) 15:08:09 ok, will take a look today 15:08:15 thx 15:08:27 so next one is almost finished: #link https://bugs.launchpad.net/neutron/+bug/1596611 15:08:28 Launchpad bug 1596611 in neutron "[RFE] Create L3 IPs with qos (rate limit)" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889) 15:08:43 there is only tempest API test patch not merged yet 15:09:13 and I found that there is probably bug with update FIP in some conditions: 15:09:13 #link https://bugs.launchpad.net/neutron/+bug/1745386 15:09:14 Launchpad bug 1745386 in neutron "Update FloatingIP to set QoS policy on it fails" [Medium,Confirmed] - Assigned to LIU Yulong (dragon889) 15:09:37 and liuyulong is on it currently AFAIK 15:09:53 mlavalle: I don't know if fix will be ready soon 15:10:11 slaweq: ok, I will keep an eye on it 15:10:34 mlavalle: I will also try to ask liuyulong about it tomorrow morning 15:11:06 and help him if he will need some help 15:11:10 ok 15:11:30 we have also already approved VPN QoS RFE: #link https://bugs.launchpad.net/neutron/+bug/1727578 15:11:31 Launchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged] 15:11:44 and specs for it #link https://review.openstack.org/#/c/531074/ 15:12:04 please add it to Your list of reviews also :) 15:12:20 I commented it yesterday already 15:12:38 generally IMO from QoS point of view it looks fine 15:12:49 that's good to know 15:13:14 but it should be reviewed by some VPN and maybe L3 experts 15:13:26 I will take a look 15:13:34 thx 15:13:54 and we have now also 2 quite similar RFEs: 15:13:55 #link https://bugs.launchpad.net/neutron/+bug/1505627 15:13:56 Launchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Triaged] - Assigned to Reedip (reedip-banerjee) 15:13:56 and 15:14:02 #link https://bugs.launchpad.net/neutron/+bug/1708460 15:14:03 Launchpad bug 1708460 in neutron " [RFE] Reaction to network congestion for qos" [Wishlist,Triaged] - Assigned to Fouad Benamrane (ftreqah) 15:14:39 mlavalle: I think that both needs some update from someone from drivers team as it was discussed recently on drivers meeting 15:14:55 first one was then approved AFAIR 15:15:26 and the second one - which is proposed by fouadben - I'm not sure about it to be honest 15:16:17 the idea is that we want to make progress on the first one 15:16:24 and postpone the second one 15:16:46 yes, that was said on drivers meeting last thursday 15:17:16 mlavalle: can You mark them with proper tags then or should I do it? 15:17:32 slaweq: I'll take care of that 15:17:37 thx a lot 15:17:54 fouadben: anything to add? 15:18:17 I don't now, I think that our proposal could enhance qos in neutron 15:18:32 By reacting to congestion using ecn. 15:18:57 Which is essential for network performance 15:19:31 could it be built on top of the other one? 15:20:44 It could be 15:20:52 but not necessary 15:21:07 so why not cooperate on the first onw 15:21:11 one 15:21:28 and then build on top after that 15:21:42 that was some of the thinking last week 15:21:57 also can't it be done with e.g. usage of heat and some metering on Neutron side? 15:22:16 for me Your specs looks like that 15:22:16 We discussed that with reedip, but we already have a proof of concept that works fine 15:23:46 Our solution based on Ovs flow table 15:25:02 At tap interface, we activate ecn and at the other side we collect ecn ce packets. 15:26:05 So, if reedip activate ecn in router that enforce ecn activation but on top of that we propose the whole process of congestion treatment. 15:27:00 I did not see why you regroup my proposal to reedip one. I did not depend on it, it is not a prerequisite for me. 15:27:37 fouadben: so Your proposal don't require ECN to be enabled in whole packet's path? 15:29:04 My proposal enable ecn in overlay layer, underlay layer is the infrastructure devices, it's outside of openstack scope I think. 15:30:42 but reedip's proposal is also about enabling ECN in overlay layer AFAIU it 15:32:00 I now, despite activating ecn, we calculate and react to the congestion. In activation phase, we enable ecn in OVS, reedip one is in the router. 15:32:11 know/now 15:32:42 ok, I will try to read Your specs once again this week 15:32:59 fouadben: are you going to Dublin? 15:33:06 thanks again 15:33:06 but I think that You will have to talk with drivers team about Your RFE also :) 15:33:20 mlavalle: no budget for it. 15:33:45 slaweq: which channel 15:33:56 fouadben: ok, so let's continue the conversation in the RFE 15:34:12 before going to the drivers meeting again 15:34:21 mlavalle: ok, no pb. 15:34:21 mlavalle: that is good idea 15:34:41 let's make sure we all understand the pros and cons 15:34:58 of both RFEs 15:35:29 ok 15:35:41 ok, so I think we can move on 15:35:48 thanks 15:35:56 it was last RFE for today 15:36:02 #topic Bugs 15:36:06 fouadben: thanks for your input and your work 15:36:16 you're wlc 15:36:27 fouadben++ 15:36:53 getting back to bugs, there is only few currently open 15:36:55 #link https://bugs.launchpad.net/neutron/+bug/1662109 15:36:56 Launchpad bug 1662109 in neutron "tempest scenario test_qos fails intermittently" [High,In progress] - Assigned to Slawek Kaplonski (slaweq) 15:37:29 I still can't check in logstash if it is still the case as there is no logs from scenario jobs there (or I don't know how to get them) 15:38:05 in couple jobs which I checked there was no such problem 15:39:03 next one was already mentioned today: #link https://bugs.launchpad.net/neutron/+bug/1745386 15:39:04 Launchpad bug 1745386 in neutron "Update FloatingIP to set QoS policy on it fails" [Medium,Confirmed] - Assigned to LIU Yulong (dragon889) 15:39:20 it is related to new feature with FIP QoS 15:39:45 next one is related only to Ocata: #link https://bugs.launchpad.net/neutron/+bug/1739411 15:39:46 Launchpad bug 1739411 in neutron "QoS DSCP mark disappear stable/ocata" [Low,Confirmed] - Assigned to Pavlukhin Max (mpavlukhin) 15:39:57 there is patch for it #link https://review.openstack.org/#/c/536095/ 15:40:22 but it's not ready for review IMHO as even UT fails there 15:40:29 ok 15:41:01 and 2 bugs where there was nothing new since last time: 15:41:06 #link https://bugs.launchpad.net/neutron/+bug/1732852 15:41:07 Launchpad bug 1732852 in neutron "neutron don't support Router gateway rate limit " [Low,In progress] - Assigned to Slawek Kaplonski (slaweq) 15:41:12 and 15:41:12 #link https://bugs.launchpad.net/neutron/+bug/1639186 15:41:13 Launchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] 15:41:28 that's all about bugs for today 15:41:32 any questions? :) 15:41:39 none from me 15:42:15 ok, so last part is 15:42:16 #topic Open Discussion 15:42:35 anyone wants to tell something? 15:42:43 I don't have anything to add here 15:42:50 me neither 15:43:17 so I guess we can finish meeting earlier 15:43:30 and enjoy few free minutes before next one :) 15:43:40 thx for attending 15:43:44 #endmeeting