Image Quota Improvement
Based on current quota design, there are some points we can improve:
1. Get quota from Keystone instead of reading from .conf
https:/
See https:/
or the quota mechanism like Nova/Cinder.
2. Add image count quota
Now we have image bytes quota and count quota for location, member, property and tag. It would be nice if we can support image count quota as well.
3. Calculate the image disk bytes exclude 'external' locations
See bug #1272837
Blueprint information
- Status:
- Not started
- Approver:
- Flavio Percoco
- Priority:
- Undefined
- Drafter:
- Feilong Wang
- Direction:
- Needs approval
- Assignee:
- Feilong Wang
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Sprints
Whiteboard
I think the general direction adopted by other projects has been to keep quota storage decentralized for performance reasons. The linked bug is wontfix. So it seems the part that is left is adding a per owner image limit, is that correct? If so, would you mind updating the summary to clarify?
markwash more-info 2014-02-17
Haven't heard back, please reassign yourself if you still want to work on it!
rosmaita abandoned 2014-03-07
