GitHub user dnezamfar closed a discussion: Issues overprovisioning CPU and memory resources because of the "disablethreshold" setting
We have 3 x 192 core / 1.5TB of RAM hosts in a single cluster/zone. We have a lot of VM's that are created with dozens of cores configured for each, but the workloads on them are very bursty and not all cores will ever be running at the same time across all the VM's on a host. I want to overcommit VM cores and RAM by a significant factor and essentially manage the resource usage myself. I have set the overprovisioning factor to 1000 to effectively stop it from preventing VM's from being started when there is ample system resources available. I still run into issues however because of the cluster disablethreshhold values, _cluster.cpu.allocated.capacity.disablethreshold_ and _cluster.memory.allocated.capacity.disablethreshold_. I want to effectively disable this so that VM's never fail to deploy when there is significant available resources. _"Cannot allocate cluster list [1] for VM creation since their allocated percentage crosses the disable capacity threshold defined at each cluster at Global Settings Configuration [name: cluster.cpu.allocated.capacity.disablethreshold, value: 1.0] for capacity Type : CPU, skipping these clusters"_ That setting is at 1.0, which is 100%, which seems to be the max? How do I set that value to 1000 or more to effectively disable it? Can I use the API? Are there any other suggestions to make sure that no setting prevents me from starting VM's because of artificial limits? GitHub link: https://github.com/apache/cloudstack/discussions/10809 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
