Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: qos rfe
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1686035
Title:
More detailed reporting of available QoS rules
Status in neutron:
New
Bug 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1686035/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
