size_iops_sec does behave different than mentioned in docs

Bug #2008762 reported by Mohammad Fatemipour
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

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.

summary: - size_iops_sec does behaves different that mentioned in docs
+ size_iops_sec does behave different than mentioned in docs
Revision history for this message
sean mooney (sean-k-mooney) wrote :

did you mean to file this to cinder.

or did you file this for disk quota in the flavor

https://github.com/openstack/nova/blob/master/nova/api/validation/extra_specs/quota.py#L149-L167

i assume for the first link
https://docs.openstack.org/cinder/latest/admin/basic-volume-qos.html
that this should be a cinder bug

Changed in nova:
status: New → Incomplete
tags: added: documentation
Revision history for this message
Sofia Enriquez (lsofia-enriquez) wrote :

Hi,
I'm going to remove Cinder from this bug. If this is wrong, please let me know why Cinder should be added to this bug.
Thanks!

no longer affects: cinder
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.