yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

This is not a bug, it's a feature request. There is likely going to be a
spec proposed for supporting passing the volume type to nova's server
create API when booting from volume and nova creates the volume, see the
ML thread here:

http://lists.openstack.org/pipermail/openstack-
dev/2016-August/102401.html

** Changed in: nova
       Status: New => Opinion

** Changed in: nova
   Importance: Undecided => Wishlist

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

Title:
  Unable to apply QoS to volume in single step while booting instance
  from image to volume.

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Currently QoS can be applied on instances with nova flavors[1]. But, it will not get applied if user is booting instance from image to volume bdm.
    
  For cinder volumes, qos specs can be associated with specified volume type after setting qos by "cinder qos-create" which can be attached to the instance[2].

  But incase of multiple volume types it's not possible to provide the
  specific volume_type during instance boot from image to volume.

  Volume_type name can be mentioned in "cinder.conf" with
  'default_volume_type' parameter incase of single volume_type.

  With this 'default_volume_type' option, if you create new instance
  from image to volume bdm, volume will get created with provided volume
  type where QoS is set.

  But, if there are multiple volume types then "default_volume_type"
  option is not valid.

  So, for cinder volumes, 2 steps needs to be performed,
  1. create volume with qos using cinder.
  2. boot from volume using nova.

  
  Can we reduce it to single step ? May be by:

  1.  providing option to select volume type while booting new instance from volume.
  Or
  2. Applying QoS defined in nova flavors to cinder volumes.


  
  [1] https://wiki.openstack.org/wiki/InstanceResourceQuota
  [2] http://paste.openstack.org/show/563825/

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