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.) Don't allow adding a host which has no capability of overcommiting resources to a cluster and we can overcommit a cluster only if all the hosts in it are capable of overcommitting.

Check if host has capabilities of overcommiting.

Almost all the hosts have the capability to overcommit, and it is up to the admin to make sure of it. Even if the host is not configured properly, cloudstack will try to set the parameters assuming it has 2.) Add the host but do not consider it for vm allocation until it is updated. if we are changing a non overcommit cluster to a overcommit cluster and if it has incapable hosts, we will allow them to be a part of the cluster but disable further allocation of VMs to these hosts until they are upgraded to have the overcommit capability.

Upgrade senario.

1.) Disable the overcommit feature in clusters existing before the upgrade. The admin should manually enable it, cloudstack will check the all the host for the overcommit capability and do the necessary.

Task Breakup

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