| Thread Previous • Date Previous • Date Next • Thread Next |
If we want to be more explicit about this in the networking-guide and
clarify the perceived side-effects of the existing implementation, then
it's fine, but this is not exactly a neutron 'bug', but a documentation
one.
** Changed in: neutron
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1521194
Title:
Qos Aggregated Bandwidth Rate Limiting
Status in neutron:
Won't Fix
Bug description:
[Existing problem]
In the current QoS implementation, network QoS bandwidth limit are applied to all the ports uniformly in the network. This may be wrong. Consider a case where the user just want 20 mbps speed for the entire network but the current implementation will end up in allowing 20 * num_of_ports_in_the_networks mbps.
[Proposal]
This proposal talks about the support for aggregated bandwidth rate limiting where all the ports in the network should together attain the specified network bandwidth limit. To start with an easiest implementation could be dividing the overall bandwidth value with the number of ports in the network. In this there might a case of over and under utilization which might need more thought (May be we got to monitor all the ports and have a notion of thresh hold to decide whether to increase or decrease the bandwidth)
[Benefits]
Better and correct user experience.
[What is the enhancement?]
Applying correct QoS rule parameter to each ports.
[Related information]
None
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521194/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
