Flavor description
Simply add a description field to the flavor resource in the data model, REST API and versioned notifications.
Being able to describe a flavor would be useful so end users don't need to understand flavor extra specs and what those mean, and for things like flavors tied to baremetal instances.
This would all be exposed in a new compute REST API microversion.
Blueprint information
- Status:
- Complete
- Approver:
- Sean Dague
- Priority:
- Low
- Drafter:
- Matt Riedemann
- Direction:
- Approved
- Assignee:
- Matt Riedemann
- Definition:
- Approved
- Series goal:
- Accepted for queens
- Implementation:
-
Implemented
- Milestone target:
-
queens-2
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Spec for flavor description
Addressed by: https:/
db: add flavors.description column
Addressed by: https:/
Add FlavorPayload.
Addressed by: https:/
WIP: Add microversion to allow setting flavor description
Addressed by: https:/
Amend flavor description spec for GET /flavors API
Addressed by: https:/
Remove compatibility method from FlavorPayload
