yahoo-eng-team team mailing list archive

[Mohammad Fatemipour <2008762@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In documentations mentioned that size_iops_sec is "burst bucket size"

https://docs.openstack.org/cinder/latest/admin/basic-volume-qos.html

but in libvirt documentations is: "The optional size_iops_sec element is
the size of I/O operations per second"

https://libvirt.org/formatdomain.html

and in qemu documentations "iops-size" described as "This setting specifies the size (in bytes) of an I/O
request for accounting purposes. Larger requests will be counted
proportionally to this size."

https://github.com/qemu/qemu/blob/master/docs/throttle.txt

so I think it is not related to burst bucket size.

and of course we do not have support for *_max_length parameters for
burst duration in nova.

** Affects: nova
     Importance: Undecided
         Status: New

** Summary changed:

- size_iops_sec does behaves different that mentioned in docs
+ size_iops_sec does behave different than mentioned in docs

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2008762

Title:
  size_iops_sec does behave different than mentioned in docs

Status in OpenStack Compute (nova):
  New

Bug description:
  In documentations mentioned that size_iops_sec is "burst bucket size"

  https://docs.openstack.org/cinder/latest/admin/basic-volume-qos.html

  but in libvirt documentations is: "The optional size_iops_sec element
  is the size of I/O operations per second"

  https://libvirt.org/formatdomain.html

  and in qemu documentations "iops-size" described as "This setting specifies the size (in bytes) of an I/O
  request for accounting purposes. Larger requests will be counted
  proportionally to this size."

  https://github.com/qemu/qemu/blob/master/docs/throttle.txt

  so I think it is not related to burst bucket size.

  and of course we do not have support for *_max_length parameters for
  burst duration in nova.

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