OpenStack Compute (nova)

Support volume_type when booting VM with block_device_mapping_v2

Bug #1596494 reported by Yi-Hsiung Chen on 2016-06-27

This bug report is a duplicate of: Bug #1400310: Booting from an image and creating a volume does not enable caller to pass volume_type. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	New	Undecided	Unassigned

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.

Revision history for this message

Yi-Hsiung Chen (bbhands-chen) wrote on 2016-06-28:

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.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1400310 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.