Instance Flavor REST API
Registered by
Sean Dague
Replace the existing "flavor" property in the "server" representation to include most of the flavor information stored with the instance, instead of the current flavor ID and link.
Blueprint information
- Status:
- Complete
- Approver:
- Matt Riedemann
- Priority:
- Medium
- Drafter:
- Sean Dague
- Direction:
- Approved
- Assignee:
- Chris Friesen
- Definition:
- Approved
- Series goal:
- Accepted for pike
- Implementation:
-
Implemented
- Milestone target:
-
pike-3
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
| Bug #1425747: User-created flavors do not enforce flavor id uniqueness | Won't Fix |
| Bug #1456196: Delete flavor should raise error, if it is inuse (any existing vms booted with this flavor) | Won't Fix |
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
add spec for instance flavor API
Addressed by: https:/
show flavor info in server details
novaclient change:
Addressed by: https:/
Add support for showing flavor details
Addressed by: https:/
update flavor info in server details spec
The novaclient CLI changes for this microversion are merged so this is complete for Pike. -- mriedem 20170627
(?)
