Make flavor id optional via flavor creation API

Bug #1071462 reported by Gabriel Hurley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Low
Russell Cloran

Bug Description

While there's a great reason to *allow* specifying the id of the flavor you're creating (e.g. you want to "replace" an existing flavor) the more common use case is actually to create a new flavor in which case you don't care what the ID is and *requiring* that the end-user specify it is actually counter-productive, confusing, and potentially frustrating.

Ideally that parameter would be optional and if not specified Nova would simply assign the flavor an unused ID automatically.

Revision history for this message
Vish Ishaya (vishvananda) wrote :

pretty easy to make flavorid optional and default it to the id value in the db or just generate a random uuid.

Changed in nova:
status: New → Triaged
importance: Undecided → Low
tags: added: low-hanging-fruit
Russell Cloran (russell)
Changed in nova:
assignee: nobody → Russell Cloran (russell)
Revision history for this message
Vish Ishaya (vishvananda) wrote :

This was actually already fixed.

Changed in nova:
status: Triaged → Invalid
Revision history for this message
Russell Cloran (russell) wrote :

As I discovered. A few related client bugs, though.

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.