-
Notifications
You must be signed in to change notification settings - Fork 89
Update ece-manage-capacity.md #1418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
thanks a lot for bringing this @frconil , and for sharing in private the reasoning behind not being able to customize the CPU quotas on Podman based installations. As talked I'll tweak a bit the changes and share them with you before merging. I'd like to:
Update: both actions have been discarded, because:
|
@kunisen , @frconil , I have a question about this change. As far as I see in the private slack conversation shared by @frconil , what we want to explain in the docs is that disabling the CPU hard limit in Podman systems is not possible. But we don't have any document that describes how to tweak the CPU hard limit (which is something we can do only in the advanced editor if i'm not mistaken). Why are we proposing this change in the doc that talks about I'm totally ok with adding a message like: But we need to ensure the message doesn't create confusion, as a reader running ECE on Docker might ask... and how can be disabled or updated in ECE running on Docker? Any proposal to make this clearer? Shouldn't this belong better (perhaps) to the Known Issues of ECE instead of the docs? Like explaining that CPU hard limit disabling doesn't really work on Podman systems? |
Oh, I think the note is applicable to the |
I've created a different PR for a different issue on the same page. We might get a small conflict when merged. On this, we are still waiting to get some responses from dev, to understand better the implication of this limitation. The text that I'm planning to propose will be similar to:
But we need to get confirmation if that's the expected outcome, like new / future instances really getting updated quota calculations or not. |
CPU quotas are not updated, and cannot be set to -1 (disable CPU hard limit) when the underlying container platform is podman.
cc @kunisen