yahoo-eng-team team mailing list archive

[Miguel Angel Ajo <majopela@xxxxxxxxxx>]

I agree with @assaf comments here,

We used kilobits to be uniform in the API.

We don't necessarily need to match the low level implementation details,
this is a high level abstraction for any plugin to implement.

What I would look at is the discrepance in "per second"

OVS talks about kBs while we talk about kb*p*s

It's not the same 10 kilobits than 10 kilobits per second. It was my
understanding when we designed the API that the burst was measured in
<UNITS> per second, but that's probably wrong.


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

-- 
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:
  Incomplete

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