Boot from image (creates a new volume) Doesn't allow specification of volume-type

Bug #1486178 reported by John Griffith
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Invalid
High
David Lyle

Bug Description

Horizon has a cool feature that wrap cinder create-volume from image and novas boot from volume all up into a single command under launch instance. The only missing thing here is the ability to specify volume-type when doing this. There should probably be a follow up that let's a user specify the cinder volume-type when using this.

David Lyle (david-lyle)
Changed in horizon:
assignee: nobody → David Lyle (david-lyle)
importance: Undecided → High
status: New → Confirmed
David Lyle (david-lyle)
Changed in horizon:
milestone: none → liberty-rc1
David Lyle (david-lyle)
Changed in horizon:
milestone: liberty-rc1 → none
Changed in horizon:
status: Confirmed → Fix Released
Revision history for this message
Erlon R. Cruz (sombrafam) wrote :

How/where is this fix released? I can't see any link for that.

Revision history for this message
David Lyle (david-lyle) wrote :

Since this is currently impossible, please don't change status to committed.

Changed in horizon:
status: Fix Released → Confirmed
Revision history for this message
Matt Riedemann (mriedem) wrote :

This is invalid for horizon because nova doesn't pass the volume_type to cinder when booting from volume and source != volume (so nova creates the volume). There is a blueprint to add that support to nova here:

https://blueprints.launchpad.net/nova/+spec/enable-volume-types

The related spec didn't make liberty and has some concerns from the nova team.

Changed in horizon:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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