<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Regarding this conversation about QoS, [1] as Nate said, we </div><div class="">have every feature x4 ( x[API, OVS, LB, SR-IOV]) and I add: we</div><div class="">should avoid writing RFEs for any missing piece in the reference</div><div class="">implementations, if any of those is missing, that’s just a bug.</div><div class=""><br class=""></div><div class="">I guess I haven’t been communicating the status and plan lately</div><div class="">neither reviewing new RFEs due to our focus on the current ones,</div><div class="">sorry about that.</div><div class=""><br class=""></div><div class="">I believe the framework we have is solid (what could I say!) but </div><div class="">we’re sticking to the features that are easier to develop on the reference</div><div class="">implementation, and still beneficial to the broadest audience</div><div class="">(like bandwidth policing, L3 marking -DSCP- , … ) and then</div><div class="">we will be able to jump into more complicated QoS rules.</div><div class=""><br class=""></div><div class="">Some of the things, are simply technically complicated in the low level</div><div class="">while very easy to model with the current framework.</div><div class=""><br class=""></div><div class="">And some of the things need integration with the nova scheduler (like</div><div class="">min bandwidth guarantees -requested by NFV/operators-) </div><div class=""><br class=""></div><div class="">After the QoS meeting I will work on a tiny report so we can raise visibility</div><div class="">about the features, and the plans.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">Miguel Ángel.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">[1] <a href="http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-02-18-22.01.log.html#l-52" class="">http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-02-18-22.01.log.html#l-52</a></div><div class=""><br class=""></div></body></html>