← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1686035] Re: [RFE] More detailed reporting of available QoS rules

 

Reviewed:  https://review.openstack.org/475260
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2cc547241c99b01e36fdc69a08c59f975b32c508
Submitter: Jenkins
Branch:    master

commit 2cc547241c99b01e36fdc69a08c59f975b32c508
Author: Sławek Kapłoński <slawek@xxxxxxxxxxxx>
Date:   Mon Jun 19 06:35:25 2017 +0000

    New API call to get details of supported QoS rule type
    
    This commit adds new API call that allows to discover
    details about supported QoS rule type and its parameters
    by each of loaded backend drivers.
    
    DocImpact: New call to get details about supported
               rule_type for each loaded backend driver
    ApiImpact
    
    Change-Id: I2008e9d3e400dd717434fbdd2e693c9c5e34c3a4
    Closes-Bug: #1686035


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
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:
  [RFE] More detailed reporting of available QoS rules

Status in neutron:
  Fix Released

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1686035/+subscriptions


References