yahoo-eng-team team mailing list archive

[Yi-Hsiung Chen <bbhands.chen@xxxxxxxxx>]

*** This bug is a duplicate of bug 1400310 ***
    https://bugs.launchpad.net/bugs/1400310

Oh, this issue is already reported at https://bugs.launchpad.net/nova/+bug/1400310
and there is an ongoing blueprint at https://blueprints.launchpad.net/nova/+spec/enable-volume-types

Sorry for reporting a duplicate one.

** This bug has been marked a duplicate of bug 1400310
   Booting from an image and creating a volume does not enable caller to pass volume_type

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

Title:
  Support volume_type when booting VM with block_device_mapping_v2

Status in OpenStack Compute (nova):
  New

Bug description:
  Will nova support specifying 'volume_type' if we boot instances with
  block_device_mapping_v2 and source_type = 'image' or 'blank',
  destination_type = 'volume' ?

  In nova/virt/block_device.py, I found that empty string is passed as volume_type in volume_api.create() calls.
  It would be nice if we can support custom volume_type and/or volume_name.

  Thanks.

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