Page History

...

But, say the allocation done till now is still within the new factor (say 0.8X is allocated currently) then allocation would still be allowed and dashboard would show 80% allocated so in this case everything seems to be correct and we should allow admin changing the factor.

What should be the behavior

...

in case of host which dose not have overcommit capability.

1.) Check if all the hosts in the cluster have the overcommit capability. If any one of the host is not capable, the cluster's overcommit ratios will remain 1 ie no overcommitAdd them to the cluster but do not consider them while deploying the VM and if host is upgraded to have this capability, we should make necessary changes to consider it for deploying VMs.

2.) Mark a cluster for overcommit while creating. Every host that is added to the marked cluster will be checked for the overcommit capability. The hosts in the unmarked clusters will not be checked and will not be allowed to use the overcommit feature. 3.) Check all the hosts for overcommit capabilities by defaultDisable overcommit feature in clusters which have hosts not capable of overcommiting the resources.

Task Breakup

Discussions with community 3 days.
updating functional spec 1 days.
Coding 4 days.
testing 2 days.