Flavor description

Registered by Matt Riedemann on 2017-09-05

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:
milestone icon queens-2
Started by
Matt Riedemann on 2017-10-24
Completed by
Matt Riedemann on 2017-11-23

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/flavor-description,n,z

Addressed by: https://review.openstack.org/501017
    Spec for flavor description

Addressed by: https://review.openstack.org/514371
    db: add flavors.description column

Addressed by: https://review.openstack.org/514782
    Add FlavorPayload.description for versioned notifications

Addressed by: https://review.openstack.org/515213
    WIP: Add microversion to allow setting flavor description

Addressed by: https://review.openstack.org/516033
    Amend flavor description spec for GET /flavors API

Addressed by: https://review.openstack.org/514943
    Remove compatibility method from FlavorPayload

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.