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
docker info shows misleading information on a CPU/RAM manually capacity-limited VCH. #1838
Comments
@mreferre This is not expected behaviour - it should show the limits if set. |
For some reason the CPU and Memory values of the pool are being treated as constant and cached. |
Ah! |
Moving to Icebox per 9/20 Triage |
I have been testing with the latest build as of today (6302). I seem to be at least able to size properly a VCH at deployment time using the new --cpu and --memory options for vic-machine. Changing values in the properties of the vApp still does not work (because of this bug). |
I will test and report @anchal-agrawal. thanks. |
@anchal-agrawal I tested it with 6507 and it works like a charm. Thanks. |
Already in the release notes, so removing the kind/note tag. |
I have deployed a VCH in the root of the cluster.
if I do a docker info it shows the whole capacity of the cluster in terms of CPU (say 13.000 Mhz) and RAM (say 127GB).
I opened the properties of the VCH vApp, unflag unlimited and I set limits for CPU and RAM (say 5.000 and 20GB).
I was expecting docker info to report now 5.000Mhz and 20GB of RAM but it keeps reporting 13.000/127GB.
Is this the expected behavior? If yes, how do we expect to segment cluster capacity? By nesting the VCH vApp into a regular vSphere RP (where we set those limits)?
The text was updated successfully, but these errors were encountered: