Unable to set flavors extra spec during creation

Bug #1322618 reported by Santiago Baldassin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Confirmed
Wishlist
Unassigned

Bug Description

Users can't set extra specs to a flavor in the creation workflow. It would be nice to add a "set extra specs" step to the creation flavor where the users can set the extra specs

Revision history for this message
Liz Blanchard (lblanchard) wrote :

Santiago,

For my own education...what would a typical entry be for setting extra specs? If this is something users would do I'm definitely in agreement it should be added as an optional step to flavor creation.

Revision history for this message
Santiago Baldassin (santiago-b-baldassin) wrote :

Hi Liz, Flavors extra specs can be use to define which host aggregate you want your vms to be launched. So if you have a host aggregate with ssd=true as part of it's metadata, then you'll need to define ssd=true as part of a flavor extra specs and select that particular flavor during the "Launch Instance" workflow.

Right now, users can set the flavors extra specs, once the flavor was created. I think that making the extra specs part of the creation workflow would be helpful

Revision history for this message
Liz Blanchard (lblanchard) wrote :

Ah, now I understand. I completely agree that this should be built into the workflow so that the user can set it up during the creation of the flavor rather than being forced to edit the flavor and define it after the fact. Thanks for this bug addition!

Liz

Revision history for this message
Gary W. Smith (gary-w-smith) wrote :

+1

Changed in horizon:
importance: Undecided → Wishlist
status: New → Confirmed
Liyingjun (liyingjun)
Changed in horizon:
assignee: nobody → Liyingjun (liyingjun)
Liyingjun (liyingjun)
Changed in horizon:
assignee: Liyingjun (liyingjun) → nobody
Changed in horizon:
assignee: nobody → Nikunj Aggarwal (nikunj2512)
Changed in horizon:
assignee: Nikunj Aggarwal (nikunj2512) → nobody
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.