yahoo-eng-team team mailing list archive

[sunzuohua <zuohuasun@xxxxxxxxx>]

Public bug reported:

For qos in neutron:
QosBandwidthLimitRule: defines the instance-egress bandwidth limit rule type, characterized by a max kbps and a max burst kbits.

API parameters are as follows:
max_kbps
max_burst_kbps


But for qos in openvswitch:
"ingress_policing_rate": the maximum rate (in Kbps) that this VM should be allowed to send.
"ingress_policing_burst": a parameter to the policing algorithm to indicate the maximum amount of data (in Kb) that this interface can send beyond the policing rate.Kb means kbytes

For example, if I create a QosBandwidthLimitRule as follows:
max_kbps = 1000
max_burst_kbps = 1000

The actual burst bandwidth is 9Mbits/sec

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Unit is not consistent for max-burst-rate

Status in neutron:
  New

Bug description:
  For qos in neutron:
  QosBandwidthLimitRule: defines the instance-egress bandwidth limit rule type, characterized by a max kbps and a max burst kbits.

  API parameters are as follows:
  max_kbps
  max_burst_kbps

  
  But for qos in openvswitch:
  "ingress_policing_rate": the maximum rate (in Kbps) that this VM should be allowed to send.
  "ingress_policing_burst": a parameter to the policing algorithm to indicate the maximum amount of data (in Kb) that this interface can send beyond the policing rate.Kb means kbytes

  For example, if I create a QosBandwidthLimitRule as follows:
  max_kbps = 1000
  max_burst_kbps = 1000

  The actual burst bandwidth is 9Mbits/sec

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