yahoo-eng-team team mailing list archive

[Assaf Muller <amuller@xxxxxxxxxx>]

The OVS documentation refers to documentation of its own implementation.
The Neutron QoS API offers an abstraction that happens to have only one
implementation at this time, but has your own LB patch
(https://review.openstack.org/236210) as a second one. As long as
something translates from the API's unit of measurement to the different
implementations unit of measurement, we're fine. We're not bound to any
one implementation's documentation.

Assigning to Miguel for further triaging.

** Changed in: neutron
     Assignee: (unassigned) => Miguel Angel Ajo (mangelajo)

** Changed in: neutron
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1507761

Title:
  qos wrong units in max-burst-kbps option

Status in neutron:
  Opinion

Bug description:
  In neutron in qos bw limit rule table in database and in API extension
  parameter "max-burst-kbps" has got wrong units suggested. Burst should
  be given in kb instead of kbps because according to for example ovs
  documentation: http://openvswitch.org/support/config-cookbooks/qos-
  rate-limiting/ it is "a parameter to the policing algorithm to
  indicate the maximum amount of data (in Kb) that this interface can
  send beyond the policing rate."

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