Bug 1262041 - QEMU Throttling of Persistent Volumes backed by RBD
QEMU Throttling of Persistent Volumes backed by RBD
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
high Severity high
: beta
: 8.0 (Liberty)
Assigned To: Eoghan Glynn
Yogev Rabl
: FutureFeature, TestOnly
Depends On:
  Show dependency treegraph
Reported: 2015-09-10 12:59 EDT by Neil Levine
Modified: 2016-04-07 17:08 EDT (History)
13 users (show)

See Also:
Fixed In Version: openstack-nova-12.0.0-1.el7ost
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-04-07 17:08:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Logs from the controllers (11.99 KB, application/x-gzip)
2016-02-10 03:36 EST, Yogev Rabl
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 22105 None None None Never

  None (edit)
Description Neil Levine 2015-09-10 12:59:10 EDT
Need to test that a max IOPS rule can be applied against a VM connected to a RBD volume managed by Cinder.
Comment 8 Stephen Gordon 2015-12-11 12:24:45 EST
"Part 3 for blueprint quota-instance-resource, by setting exposed params
"disk_read_bytes_sec, disk_read_iops_sec, disk_write_bytes_sec,
disk_write_iops_sec, disk_total_bytes_sec, disk_total_iops_sec"
through nova flavor-set, user can implement instance disk IO control
for example:
nova flavor-set m1.medium set disk_write_bytes_sec=10240000,
then the max disk write IO is 10MB/s for VM user."
Comment 9 Yogev Rabl 2016-02-09 10:51:06 EST
The verification failed with the following packages: 

My steps were:
1. added the property from comment 8
# nova flavor-key m1.tiny set disk_write_bytes_sec=10240000
2. tried to launch an instance
3. tried to launch an instance with a flavor with similar values as the tiny flavor, without the additional property and the instance launch was successful
Comment 10 Stephen Gordon 2016-02-09 11:31:08 EST
Yogev please provide logs and more information on what the error was in (2). Also can you confirm that while the steps are listed as being manually executed this is also being added to automation?


Comment 11 Yogev Rabl 2016-02-10 03:36 EST
Created attachment 1122709 [details]
Logs from the controllers

Adding the log from the controllers and the details of the instance.
Comment 12 Stephen Gordon 2016-02-10 04:33:35 EST
(In reply to Stephen Gordon from comment #8)
> nova flavor-set m1.medium set disk_write_bytes_sec=10240000,
> then the max disk write IO is 10MB/s for VM user."

Thanks Yogev, one other thing. I notice you used this command to set the throttling level:

$ nova flavor-set m1.medium set disk_write_bytes_sec=10240000

Can you try again with this:

$ nova flavor-set m1.medium set quota:disk_write_bytes_sec=10240000

The request appears to be failing out of the ComputeCapabilitiesFilter, I am wondering if this is because the lack of the quota: namespacing results in it being picked up by the wrong filter.


Comment 13 Yogev Rabl 2016-02-10 05:54:52 EST
Hi Steve, 

Checked it with the modification - it works well.
The disk configuration of the instance is: 

    <disk type="network" device="disk">
      <driver type="raw" cache="none"/>
      <source protocol="rbd" name="vms/3084fd6a-64b1-4560-ba0b46792d21418d_disk">
        <host name="" port="6789"/>
        <host name="" port="6789"/>
        <host name="" port="6789"/>
      <auth username="openstack">
        <secret type="ceph" uuid="84099bea-c9db-11e5-a169-52540097887b"/>
      <target bus="virtio" dev="vda"/>

changing to verify.
Comment 14 Stephen Gordon 2016-02-10 06:11:15 EST
Thanks Yogev, just following up on one other earlier question - does this mean we now also have automation coverage of this feature?
Comment 15 Yogev Rabl 2016-02-10 06:59:48 EST
No, we don't have an automated test for this feature at the moment. It will be automated in the near future. 

We do have a test plan for it ready
Comment 17 errata-xmlrpc 2016-04-07 17:08:09 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.