Comment 9 for bug 1936408
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Hello:
I'm reopening this RFE again and I hope next Friday I'll have time to present it in the driver's meeting.
The goal of this RFE is NOT to change the default API behaviour but to provide an alternative one. I initially presented several alternatives but none of them were good enough, due to how quota engine is loaded and the lack of defined API (it is created during the module load).
What I'm proposing is to add a new parameter to the CLI that triggers the check (and possible rejection) of the new quota limit. To provide some context, Nova do not allow to lower a quota limit below the current usage. However it is possible to override a limit using the CLI parameter "force" [1]. The proposal is just the opposite to what Nova implements: a new parameter (e.g.: "check-limit") that will be passed in the CLI command. if this parameter is present, the Neutron quota engine will check the current quota usage and limit and will reject, if needed, the quota update (same as in Nova).
Regards.
[1]https:/