Allow custom resource classes in flavor extra specs
Allows a flavor to request custom resource classes via extra specs, and also allows overriding of "standard" resource classes (VCPU, MEMORY_MB, DISK_GB) in extra specs such that they can be displayed in API fields (and CLI/dashboard/etc) without being scheduled to.
Blueprint information
- Status:
- Complete
- Approver:
- Sylvain Bauza
- Priority:
- High
- Drafter:
- Jim Rollenhagen
- Direction:
- Approved
- Assignee:
- Ed Leafe
- 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 #1701530: Extract custom resource classes from flavors | Confirmed |
Bug #1707021: Ironic Flavor Migration can miss instances | Fix Released |
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add spec for custom resource classes in flavors
Jay is getting stretched thin on other work, so we probably need one or more people to step up and own this one which sounds like at least three major changes: placement API updates for filtering resource providers by custom resource class, a change in the FilterScheduler to pass those through via flavor extra specs, and a data migration for Ironic instances. cdent and edleafe expressed interest in owning this during the June 12 nova-scheduler meeting. dtantsur from Ironic said he could help with black box integration testing. -- mriedem 20170712
I don't think any changes need to be made to the placement API. It currently accepts a generic 'resources' query parameter, and can handle any number of {resource_class: amount} key-value pairs. -- edleafe 2017.06.13
Addressed by: https:/
Extract custom resource classes from flavors
Gerrit topic: https:/
Addressed by: https:/
Amend spec for "Allow custom resource classes in flavor extra specs"
Addressed by: https:/
Consider instance flavor resource overrides in allocations
Addressed by: https:/
WIP - Migrate Ironic Flavors
Addressed by: https:/
Remove the Pike migration code for flavor migration
Gerrit topic: https:/
Addressed by: https:/
ironic: complete the flavor data migration started in pike
Work Items
Dependency tree

* Blueprints in grey have been implemented.