← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1445637] Re: Instance resource quota not observed for non-ephemeral storage

 

I'm sorry for I was too hurry to change into invalid. 
Originally I was thought those non-ephemeral disk was managed by cinder, those settings should dependent on it.
And even you assign higher value, the rate was still limit by cinder. Then you can't observed the real rate.
But I also thought flavor was hardware template, its settings should also apply.
Maybe we could select the minimum quota value between cinder or flavor settings.

** Changed in: nova
       Status: Invalid => In Progress

-- 
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/1445637

Title:
  Instance resource quota not observed for non-ephemeral storage

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  I'm using a nova built from stable/kilo and trying to implement
  instance IO resource quotas for disk as per
  https://wiki.openstack.org/wiki/InstanceResourceQuota#IO.

  While this works when building an instance from ephemeral storage, it
  does not when booting from a bootable cinder volume. I realize I can
  implement this using cinder quota but I want to apply the same
  settings in nova regardless of the underlying disk.

  Steps to produce:

  nova flavor-create iolimited 1 8192 64 4
  nova flavor-key 1 set quota:disk_read_iops_sec=10000
  Boot an instance using the above flavor
  Guest XML is missing <iotune> entries

  Expected result:
  <snip>
        <target dev='vda' bus='virtio'/>
        <iotune>
          <read_iops_sec>10000</read_iops_sec>
        </iotune>
  </snip>

  This relates somewhat to https://bugs.launchpad.net/nova/+bug/1405367
  but that case is purely hit when booting from RBD-backed ephemeral
  storage.

  Essentially, for non-ephemeral disks, a call is made to
  _get_volume_config() which creates a generic LibvirtConfigGuestDisk
  object but no further processing is done to add extra-specs (if any).

  I've essentially copied the disk_qos() method from the associated code
  review (https://review.openstack.org/#/c/143939/) to implement my own
  patch (attached).

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


References