DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.

DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Going to test for following hypervisore |
|
|
|
|
|
|
|
|
|
|
Test Case ID | Test Case Name | Steps | Expected Result | Priority | Test Case Type | Automatable(Y/N) | VMWARE(Y/N) | KVM(Y/N) | XEN(Y/N) | OVM(Y/N) | BAREMETAL(Y/N) |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 | 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| Where host cpu overcommit capabilities<cluster cpu overcommit |
| 1-CS should not allow addition of host |
|
|
| Y | Y | Y | N | N |
| where host cpu overcommit capabilities >= cluster cpu overcommit |
| 1-CS should allow addition of host |
|
|
| Y | Y | Y | N | N |
| where host RAM overcommit capabilities<cluster RAM overcommit |
| 1-CS should not allow addition of host |
|
|
| Y | Y | Y | N | N |
| where host RAM overcommit capabilities >= cluster RAM overcommit |
| 1-CS should allow addition of host |
|
|
| Y | Y | Y | N | N |
| where host CPU and RAM overcommit capabilities<cluster CPU and RAM overcommit |
| 1-CS should not allow addition of host |
|
|
| Y | Y | Y | N | N |
| where host CPU and RAM overcommit capabilities >= cluster CPU andRAM overcommit |
| 1-CS should allow addition of host |
|
|
| Y | Y | Y | N | N |
| Where host cpu overcommit capabilities<cluster cpu overcommit |
| 1-CS should allow addition of host |
|
|
|
|
|
|
|
|
| Overcommit factor conflict effect on vms |
|
|
|
|
|
|
|
|
|
|
|
| 1-Already deployed vm should not have any effect |
|
|
| Y | Y | Y | N | N | |
| Overcommit factor conflict effect on host in cluster |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| where host cpu overcommit cpabilities < new cpu overcommit factor | 1-host should remain in cluster, but should not be available for vm deployment |
|
|
| Y | Y | Y | N | N | |
| where host cpu overcommit cpabilities >= new cpu overcommit factor | 1-host should remain in cluster, but should be available for vm deployment |
|
|
| Y | Y | Y | N | N | |
| where host ram overcommit cpabilities < new ram overcommit factor |
|
|
|
|
| Y | Y | Y | N | N |
| where host ram overcommit cpabilities >= new ram overcommit factor |
|
|
|
|
| Y | Y | Y | N | N |
| where host cpu and ram overcommit cpabilities < new cpu and ram overcommit factor |
|
|
|
|
| Y | Y | Y | N | N |
| where host CPU and RAM overcommit cpabilities >= new cpu and ram overcommit factor |
|
|
|
|
| Y | Y | Y | N | N |
| Upgrade from 4.0 to 4.1 |
|
|
|
|
|
|
|
|
|
|
| upgrade path | 1-Disable overcommit feature and do normal upgrade | 1- Upgrade should be successful . |
|
|
|
|
|
|
|
|