Refresh quotas usage
For some reasons*, the quotas usage can be out of sync.
When a quota is wrongfully reached, a user cannot launch new VMs anymore.
This "refresh" feature allows operators to quickly unblock users without
manually running queries against the database or temporarily increase the
quota.
[*] It seems that there are several root causes and there is no procedure
to reproduce bugs. Although these root causes will eventually be
identified, we cannot guarantee that some bugs will not occur again.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Romain Hardouin
- Direction:
- Approved
- Assignee:
- Chuck Carmack
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
-
newton-2
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Refresh quotas usage
Please note this blueprint will delayed until the M release if it is not in the NeedsCodeReview state (with all the code up for review) before July 16th, and merged by July 30th. We expect to re-open master for the M release in September. For more information, please see: https:/
--johnthetubaguy 15th July 2015
Unapproved for liberty due to the Non-Priority Feature Proposal Freeze. --johnthetubaguy 16th July 2015
Addressed by: https:/
Re-propose spec for refresh-
Sorry, we have now hit the Non-Priority Feature Freeze for Mitaka. For more details please see: http://
--johnthetubaguy 2016.01.31
Addressed by: https:/
Re-propose spec for refresh-
Addressed by: https:/
Add nova-manage quota_usage_refresh command
Addressed by: https:/
Database API changes for the nova-manage quota_usage_refresh command
Addressed by: https:/
Quota driver changes for the nova-manage quota_usage_refresh command
Addressed by: https:/
Add nova-manage quota_usage_refresh command
Addressed by: https:/
DB API changes for the nova-manage quota_usage_refresh command
