quotas on number of users and projects per domain
A cloud provider allowing customers to create projects and users inside dedicated domains might be interested in having the possibility to define restrictions on the amount of projects and users that can be created per domain.
These quotas could be set in keystone's configuration file.
When creating a project, there would be a check of how many projects are already existing for the associated domain. If the domain has met the projects quota, the creation query is rejected.
When creating a user, there would be a check of how many users are already existing for the associated domain. If the domain has met the users quota, the creation query is rejected.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
sjcazzol 4.22.14 - Initial specification done to check the direction: https:/
sjcazzol 4.22.14 - I would to add this to the description:
To address this, I propose to add a quota management mechanism which will manage
two resources (users, projects). The quotas will be set at domain level.
This quota system will add a capability in order to allow cloud providers to charge
based on the number of projects/users that use the platform.
Also another advantage is to protect the platform against some performance issues.
