Page History

UI/API check

1-Add cluster using  API addCluster

add cluster API should have new parameters  cpuovercommitratio and ramovercommitratio

UI/API check

1- Fire API UpdateOvercommitRatio with parameter cpuovercommitratio,ramovercommitratio.

response should contain " details of the updated cluster along with the overcommit ratios"

DB check

1-Logoin through UI
2-create a cluster with overcommit factor x
3-Login to DB
4-check cluster detail table

1-There should be some attribute ,which  represent overcommit factor and should have store overcommit factor for the clusters .

Addition of host to a cluster with
cpu overcommit capabilities<cluster cpu overcommit

1-CS should not allow addition of host

Addition of host to a cluster with
cpu overcommit capabilities >= cluster cpu overcommit

1-CS should  allow addition of host

Addition of host to a cluster with
RAM overcommit capabilities<cluster RAM overcommit

1-CS should not allow addition of host

Addition of host to a cluster with
RAM overcommit capabilities >= cluster RAM overcommit

1-CS should  allow addition of host

Addition of host to a cluster with
CPU and RAM overcommit capabilities<cluster CPU and RAM overcommit

1-CS should not allow addition of host

Addition of host to a cluster with
CPU and RAM overcommit capabilities >= cluster CPU andRAM overcommit

1-CS should  allow addition of host

Overcommit factor  conflict for xen

1-Already deployed vm should not have any effect
2-only vm deployed here after should get deployed based on new Overcommit factor.

Overcommit factor  conflict for VMware

1-Already deployed vm should not have any effect
2-only vm deployed here after should get deployed based on new Overcommit factor.

Overcommit factor  conflict for KVM

1-Already deployed vm should not have any effect
2-only vm deployed here after should get deployed based on new Overcommit factor.