yahoo-eng-team team mailing list archive

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

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New

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