The newer version of vOneCloud has improved the overcommitment definition by bettering the interface.
In this thread https://support.vonecloud.com/hc/en-us/community/posts/206487919-Template-in-PENDING-state I was looking at the problem of handling overcommitment of CPU resources. The solution then was to hack some values in the RESERVED_CPU cluster settings with higher and higher negative values.
VoC support mentioned this was going to be revised for the next release, so can you explain how be manage overcommitment of CPU resources now? There seem to be settings per Resource Pool, but it would be useful to know how they work now as the RESERVED_CPU and RESERVED_MEM parameters are no longer listed.
I have plenty of spare 'real' capacity, yet the ALLOCATED_CPU parameter is already showing 7200/9800 (72%) with less than 30 provisioned VM's.
Please sign in to leave a comment.
Thanks for the update. Any idea what version this will be available in? I'm currently running v2.01. Is 2.02 on the way?
This is present in 2.0.1, is this not showing for you?
Thanks. After digging around, yes, I can now see those settings for overcommitt in 2.0.1. For CPU, it seems to default to -5000. What does this figure represent? Would doubling this to -10000 cause any problems?
There is no default value in vOneCloud, the -5000 must have been set previously?
Values are given in CPU percentage, so -5000 corresponds to a 50 CPU overcommitment.