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) | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | UI/API check | 1-Add cluster using API addCluster | add cluster API should have new parameters cpuovercommitratio and ramovercommitratio | P0 |
| Y |
|
|
|
|
| ||
2 | UI/API check | 1- update commit ratio using API UpdateOvercommitRatio with parameter cpuovercommitratio,ramovercommitratio. | response should contain " details of the updated cluster along with the overcommit ratios" | P0 |
| Y |
|
|
|
|
| ||
3 | 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 . | P0 |
| Y |
|
|
|
|
| ||
| Addition of host to a cluster |
|
|
|
|
|
|
|
|
| 4 | ||
1-Login through UI |
|
|
|
|
|
|
|
|
| ||||
4 5 | 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 | Y | N | N | ||
5 6 | 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 | Y | N | N | ||
6 7 | 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 | Y | N | N | ||
6 8 | 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 | Y | N | N | ||
7 9 | 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 | Y | N | N | ||
8 10 | 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 | Y | N | N | ||
9 11 | 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 | Y | N | N | ||
12 10 | 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 | Y | N | N | ||
13 11 | 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 | Y | N | N | ||
| Overcommit factor conflict effect on vms |
|
|
|
|
|
|
|
|
| |||
| 1-Login Through UI |
|
|
|
|
|
|
|
|
| |||
14 12 | 5-when y<x and there is no(less than required) resource left in cluster according to new overcommit ratio | 1-VM deployed in step 3 should not have any effect of y | P0 | Functional | Y | Y | Y | Y | N | N | |||
15 13 |
| 5-when y<x and there is enough resource left in cluster according to new overcommit ratio | 1-VM deployed in step 3 should not have any effect of y | P0 | Functional | Y | Y | Y | Y | N | N | ||
16 14 |
| 5-when y>x and there is enough resource left in cluster according to new overcommit ratio | 1-VM deployed in step 3 should not have any effect of y | P0 | Functional | Y | Y | Y | Y | N | N | ||
17 15 |
| 5-when y>x and there is not enouh resource left in cluster according to new overcommit ratio | 1-VM deployed in step 3 should not have any effect of y | P0 | Functional | Y | Y | Y | Y | N | N 18 | ||
|
|
|
|
|
|
|
|
|
|
| |||
| Overcommit factor conflict effect on host in cluster |
|
|
|
|
|
|
|
|
| |||
|
| 1-Login through UI |
|
|
|
|
|
|
|
|
| ||
16 19 | where host cpu overcommit capabilities < updated cpu overcommit factor and | when c<x and r<y | 1-host should remain in cluster, but should not be available for vm deployment |
| Functional | Y | Y | Y | Y | N | N | ||
17 20 | where host cpu overcommit capabilities < updated cpu overcommit factor and | 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 | Y | N | N | ||
18 21 | where host cpu overcommit capabilities < updated cpu overcommit factor and | 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 | Y | N | N | ||
19 22 | where host cpu overcommit capabilities > updated cpu overcommit factor and | 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 | Y | N | N | ||
23 20 | where host cpu overcommit capabilities > updated cpu overcommit factor and | when c>x and r>y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional | Y | Y | Y | Y | N | N | ||
24 21 | where host cpu overcommit capabilities > updated cpu overcommit factor and | when c>x and r=y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional | Y | Y | Y | Y | N | N | ||
25 22 | where host cpu overcommit capabilities = updated cpu overcommit factor and | 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 | Y | N | N | ||
26 23 | where host cpu overcommit capabilities = updated cpu overcommit factor and | when c=x and r>y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional | Y | Y | Y | Y | N | N | ||
27 24 | where host cpu overcommit capabilities = updated cpu overcommit factor and | when c=x and r=y | 1-host should remain in cluster, and should be available for vm deployment | P0 | Functional | Y | Y | Y | Y | N | N | ||
| Upgrade from 4.0 to 4.1 |
|
|
|
|
|
|
|
|
| |||
28 25 | upgrade path | Pre upgrade steps | 1- Upgrade should be successful . |
| Upgrade | Y | Y | Y | Y | N | N | ||
| Effect of contention on vms |
|
|
|
|
|
|
|
|
|
| ||
26 29 | CPU contention |
| VM should get assigne to CPU=(CPU define in SO/CPU overcommit factor) | P1 | Functional | Y | Y | Y | Y | N | N | ||
27 30 | RAM contention |
| VM should get assigne to RAM=(RAM define in SO/RAM overcommit factor) | P1 | Functional | Y | Y | Y | Y | N | N | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f6ab698fd65ba7f5-5e0f1d7f-477140db-a885bc28-56217371cd7aacf9e9d663a5"><ac:plain-text-body><![CDATA[ | 28 31 | CPU and RAM contention |
| VM should get assigne to (CPU/RAM)=[(CPU/RAM) define in SO/(CPU/RAM) overcommit factor] | P1 | Functional | Y | Y | Y | Y | N | N | ]]></ac:plain-text-body></ac:structured-macro> |
29 32 | Dash board resource display | physical availability or logical(in case of overcommit) | yet to decide | P2 | Functional |
|
|
|
|
|
|