Comment 4 for bug 1386911
Revision history for this message
| Syed Mohammad Adnan Karim (karimsye) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
@Ryan
* Operators typically set quotas post-deployment via the CLI. What happens to that custom tuning when the quota configs are changed on the charm, post-deployment?
Answer: Custom quotas set through CLI are unchanged
* Does that conflict with, or potentially revert any post-deployment quota settings which have been set by an operator through the CLI?
Answer: Post deployment quota settings are not changed
* How does changing the quota charm config impact existing projects/tenants?
Answer: New projects will have the new changed settings from the charm config.
Existing projects that that had their quotas modified will retain their values.
Projects whose quotas were not modified will update to the new settings.
* What happens in a charm upgrade scenario where the older charm did not have these values set, and they were not rendered into the config via a template, and the newer charm does declare these values, and does render the config template? Could new quotas be imposed unexpectedly? Or could an operators' tuned quota configs change unexpectedly?
Answer: New projects will have the new changed settings from the charm config.
Existing projects that that had their quotas modified will retain their values.
Projects whose quotas were not modified will update to the new settings.