Domain Quota Management to allow domain quotas to be managed and enforced
In Keystone v3 (Grizzly release), the domain encapsulates users and projects into logical entities that can represent accounts, organizations, etc. Currently there is no capability or mechanism to manage or enforce quotas at domain level. Assigning or updating quota values or limits to a domain will allow the cloud administrator to evaluate domain lists and consumption. In order to achieve these capabilities it will be required to implement quota management for Keystone domains. The goal of this blueprint is to support quotas at the OpenStack Domain level. The design of the feature models, as far as possible, the style of project quotas.
HP is working closely with Cern (Ulrich Schwickerath) and BARC (Akshat Kakkar) on the design, api specification, and implementation.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Tiago Martins
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- Yehia Beyh
- Completed by
- Dolph Mathews
Whiteboard
Our design proposes a central storage for quotas in the like of Keystone Store Quota Data[1] to stor, for now, domain quotas. *It can be used to store any other type of quota.*
[1] https:/
Gerrit topic: https:/
Addressed by: https:/
Domain Quota Management and Enforcement
Marking quota bp's as Obsolete and untargeted for icehouse, as a complete lack of interest in utilizing centralized quota storage was expressed by the other PTLs during today's cross-project #openstack-meeting -dolph
Work Items
Work items:
Keystone REST API: DONE
Keystone REST API unit tests: DONE
Keystone DB methods: DONE
Keystone DB methods unit tests: DONE
Dependency tree
* Blueprints in grey have been implemented.
