[Yahoo-eng-team] [Bug 1507761] Re: qos wrong units in max-burst-kbps option (per-second is wrong)

2016-05-18 Thread Miguel Angel Ajo
As per review discussion, this can't really be done until we had API microversioning, deferring until then. ** Changed in: neutron Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron.

[Yahoo-eng-team] [Bug 1507761] Re: qos wrong units in max-burst-kbps option

2016-02-24 Thread Miguel Angel Ajo
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

[Yahoo-eng-team] [Bug 1507761] Re: qos wrong units in max-burst-kbps option

2015-10-19 Thread Assaf Muller
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