yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #91445
[Bug 2008762] Re: size_iops_sec does behave different than mentioned in docs
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
** Also affects: cinder
Importance: Undecided
Status: New
** Tags added: documentation
--
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 Cinder:
New
Status in OpenStack Compute (nova):
Incomplete
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/cinder/+bug/2008762/+subscriptions
References