Never change quota schema again
Registered by
Mark Washenberger
Currently, the quota table in the nova db has a column for every type of quota we manage. Thus, each time we add a new type of quota to the system, we have to make a schema change. I propose that we switch to a key-value approach for quotas so that adding new types of quotas does not require a schema change.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Titan
- Definition:
- New
- Series goal:
- Accepted for diablo
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Vish Ishaya
- Completed by
- Vish Ishaya
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.