| 2017-04-25 07:36:02 |
Slawek Kaplonski |
bug |
|
|
added bug |
| 2017-04-25 07:36:15 |
Slawek Kaplonski |
neutron: assignee |
|
Slawek Kaplonski (slaweq) |
|
| 2017-04-25 18:49:08 |
Miguel Lavalle |
neutron: importance |
Undecided |
Medium |
|
| 2017-04-25 18:49:25 |
Miguel Lavalle |
neutron: status |
New |
Triaged |
|
| 2017-04-27 20:10:52 |
Slawek Kaplonski |
summary |
More detailed reporting of available QoS rules |
[RFE] More detailed reporting of available QoS rules |
|
| 2017-04-28 06:31:36 |
Slawek Kaplonski |
description |
Currently Neutron has API call "qos-available-rule-types" which will return subset of pos rules supported by all loaded drivers (openvswitch, linuxbridge, etc.)
After https://bugs.launchpad.net/neutron/+bug/1586056 was closed it's not enough and some changes should be done with it.
1. qos-available-rule-types should return subset of rules supported by ANY of loaded drivers, not by all drivers. This should be changed because now if rule is supported by at least on of drivers than it can be used and applied to ports bound with this driver. Neutron will not allow to apply such rule to other ports.
2. Some new API call should be added to report details about supported rules. It should returns something like
+--------+---------------------+----------------------------+
| Driver | Supported rule | Supported parameters |
+--------+---------------------+----------------------------+
| ovs |bandwidth_limit_rule | direction: egress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
| LB |bandwidth_limit_rule | direction: egress, ingress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
Thanks to that API call operator will be able to discover exactly which rules and with what values can be applied to ports bound with specific driver. |
Currently Neutron has API call "qos-available-rule-types" which will return subset of pos rules supported by all loaded drivers (openvswitch, linuxbridge, etc.)
After https://bugs.launchpad.net/neutron/+bug/1586056 was closed it can be not enough sometimes.
I would suggest to add new API call to report details about supported rules. It should returns something like
+--------+---------------------+----------------------------+
| Driver | Supported rule | Supported parameters |
+--------+---------------------+----------------------------+
| ovs |bandwidth_limit_rule | direction: egress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
| LB |bandwidth_limit_rule | direction: egress, ingress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
Thanks to that API call operator will be able to discover exactly which rules and with what values can be applied to ports bound with specific driver.
As such call can leak used driver names to the users it should be available only for admins. |
|
| 2017-05-18 21:30:01 |
Ihar Hrachyshka |
description |
Currently Neutron has API call "qos-available-rule-types" which will return subset of pos rules supported by all loaded drivers (openvswitch, linuxbridge, etc.)
After https://bugs.launchpad.net/neutron/+bug/1586056 was closed it can be not enough sometimes.
I would suggest to add new API call to report details about supported rules. It should returns something like
+--------+---------------------+----------------------------+
| Driver | Supported rule | Supported parameters |
+--------+---------------------+----------------------------+
| ovs |bandwidth_limit_rule | direction: egress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
| LB |bandwidth_limit_rule | direction: egress, ingress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
Thanks to that API call operator will be able to discover exactly which rules and with what values can be applied to ports bound with specific driver.
As such call can leak used driver names to the users it should be available only for admins. |
Currently Neutron has API call "qos-available-rule-types" which will return subset of qos rules supported by all loaded drivers (openvswitch, linuxbridge, etc.)
After https://bugs.launchpad.net/neutron/+bug/1586056 was closed it can be not enough sometimes.
I would suggest to add new API call to report details about supported rules. It should returns something like
+--------+---------------------+----------------------------+
| Driver | Supported rule | Supported parameters |
+--------+---------------------+----------------------------+
| ovs |bandwidth_limit_rule | direction: egress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
| LB |bandwidth_limit_rule | direction: egress, ingress |
| | | max_kbps: ANY VALUE |
+--------+---------------------+----------------------------+
Thanks to that API call operator will be able to discover exactly which rules and with what values can be applied to ports bound with specific driver.
As such call can leak used driver names to the users it should be available only for admins. |
|
| 2017-05-18 21:32:26 |
Miguel Lavalle |
neutron: importance |
Medium |
Wishlist |
|
| 2017-06-15 22:14:46 |
Kevin Benton |
tags |
qos rfe |
qos rfe-approved |
|
| 2017-06-19 06:37:43 |
OpenStack Infra |
neutron: status |
Triaged |
In Progress |
|
| 2017-07-12 20:22:03 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2018-02-28 21:55:16 |
Akihiro Motoki |
neutron: milestone |
|
pike-3 |
|
