Comment 12 for bug 1936408
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hello Brian:
First of all, let me highlight that what I'm proposing will NOT change the default behaviour. That means, any user script using "openstack" CLI will be affected.
What I'm going to propose on Friday is to add to the CLI a new parameter for "network" commands. To document this parameter I provided [1] as an example: a parameter only for "compute" commands that modifies the command behaviour.
**BUT** this is an example of implementation. What I'm proposing is the opposite: a new CLI parameter, only for "network" commands, that will enforce the quota check, something we currently don't do. This parameter could be called "check-quota" (for example, I'm very bad at naming):
- If this new parameter is added to the command, the Neutron server will check the new quota limit provided and fail if needed.
- If this new parameter is not provided, we'll work as usual; that means we'll be able to lower the quota limit without any check (as is now).
Again, I'm not proposing a default behaviour change. What I'm proposing is adding a new parameter that will trigger the quota limit check.
NOTE: this is the default behaviour in Nova. Nova cannot lower a resource limit (VCPUS for example) if VMs are using more. However, Nova is able to lower this limit using "--force" [1].
Regards.
[1]https:/