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.
| This feature is implemented for following hypervisor |
|
|
|
|
|
|
|
|
|
| ||
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 |
|
|
|
|
|
|
|
|
|
| ||
| 1-Login through UI |
|
|
|
|
|
|
|
|
| |||
| Where host cpu overcommit capabilities<cluster cpu overcommit factore and | 4--Add host to cluster where c <x and r<y | 1-CS should not allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities<cluster cpu overcommit factore and | 4-Add host to cluster where c <x and r>y | 1-CS should not allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities<cluster cpu overcommit factore and | 4-Add host to cluster where c<x and r=y | 1-CS should not allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities>cluster cpu overcommit factore and | 4-Add a host to cluster where c>x and r<y | 1-CS should not llow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities>cluster cpu overcommit factore and | 4-Add a host to cluster where c >x and r>y | 1-CS should allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities>cluster cpu overcommit factore and | 4-Add host to cluster where c>x and r=y | 1-CS should allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities=cluster cpu overcommit factore and | 4-Add host to cluster where c=x and r<y | 1-CS should not allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities=cluster cpu overcommit factore and | 4-Add host to cluster where c=x and r>y | 1-CS should allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Where host cpu overcommit capabilities=cluster cpu overcommit factore and | 4-Add host to cluster where c=x and r=y | 1-CS should allow addition of host | P0 | Functional |
| Y | Y | Y | N | N | ||
| Overcommit factor conflict effect on vms | 1-Login Through UI |
|
|
|
|
|
|
|
|
| ||
5-when y<x and there is no(less than required) resource left in cluster according to new overcommit ratio |
| 1-Login through UI | 1-VM deployed in step 3 should not have any effect of y new overcommit factor |
|
|
|
|
|
|
|
| ||
|
| 2- After step 5 Resources availability in cluster should be based on new overcommit ratio. | P0 | Functional |
| Y | Y | Y | N | N | |||
|
| 5-when y<x and there is enough resource left in cluster according to new overcommit ratio where c <x and r>y | P0 |
|
|
|
|
|
|
| |||
|
| 5-where c <x and r=y | P0 |
|
|
|
|
|
|
| |||
|
| 5-when y>x and there is enough resource left in cluster according to new overcommit ratio where c >x and r<y | P0 |
|
|
|
|
|
|
| |||
|
|
| P0 |
|
|
|
|
|
|
| |||
|
| 5-when y>x and there is not enouoh resource left in cluster according to new overcommit ratio where c >x and r=y | 1-In step 6 vm should not get deployed | P0 |
|
|
|
|
|
|
| ||
|
| 5- where c =x and r>y |
| P0 |
|
|
|
|
|
|
| ||
|
| 5-when y=x and there is enouogh resource left in cluster according to new overcommit ratio where c =x and r<y | 1-In step 6 vm should get deployed |
| P0 |
|
|
|
|
|
|
| |
|
| 5-when y=x and there is not enouogh resource left in cluster according to new overcommit ratio where c =x and r=y | 1-In step 6 vm should not get deployed |
| P0 |
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| ||
| Overcommit factor conflict effect on host in cluster | 1-Login through UI |
|
|
|
|
|
|
|
|
| ||
| when c<x and r<y | 1-host should remain in cluster, but should not be available for vm deployment |
|
|
|
|
|
|
|
| |||
| where host cpu overcommit cpabilities < new cpu overcommit factor | when c<x and r>y | 1-host should remain in cluster, but should not be available for vm deployment | P0 | Functional |
| Y | Y | Y | N | N | ||
| where host cpu overcommit cpabilities >= new cpu overcommit factor | when c<x and r=y | 11-host should remain in cluster, but should not be available for vm deployment | P0 | Functional |
| Y | Y | Y | N | N | ||
| where host ram overcommit cpabilities < new ram overcommit factor | when c>x and r<y | 1-host should remain in cluster, but should not be available for vm deployment | P0 | Functional |
| Y | Y | Y | N | N | ||
| where host ram overcommit cpabilities >= new ram overcommit factor | when c>x and r>y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional |
| Y | Y | Y | N | N | ||
| where host cpu and ram overcommit cpabilities < new cpu and ram overcommit factor | when c>x and r=y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional |
| Y | Y | Y | N | N | ||
| where host CPU and RAM overcommit cpabilities >= new cpu and ram overcommit factor | when c=x and r<y | 1-host should remain in cluster, but should not be available for vm deployment | P0 | Functional |
| Y | Y | Y | N | N | ||
|
| when c=x and r>y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional |
| Y | Y | Y | N | N | ||
|
| when c=x and r=y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional |
| 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 . |
|
|
|
|
|
|
|
| ||
| Effect of contention on vms |
|
|
|
|
|
|
|
|
|
| ||
| CPU contention |
| VM should get assigne to CPU=(CPU define in SO/CPU overcommit factor) | P1 | Functional |
|
|
|
|
|
| ||
| RAM contention |
| VM should get assigne to RAM=(RAM define in SO/RAM overcommit factor) | P1 | Functional |
|
|
|
|
|
| ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b05b3ddfe228e489-e4619eb3-426a4d81-a98889b1-04cdf3f9e863eee1b37fa06f"><ac:plain-text-body><![CDATA[ |
| CPU and RAM contention |
| VM should get assigne to (CPU/RAM)=[(CPU/RAM) define in SO/(CPU/RAM) overcommit factor] | P1 | Functional |
|
|
|
|
|
| ]]></ac:plain-text-body></ac:structured-macro> |
| Dash board resource display | physical availability or logical(in case of overcommit) | yet to decide | P2 | Functional |
|
|
|
|
|
|