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 |
|
|
|
|
| ||
4 | Addition of host to cluster(with ram overcommit >1 and cpu overcommit =1) | add a host(which supports ram overcommit but not CPU) to cluster | 1- CS should add host to cluster | P0 |
| y |
|
|
|
|
| ||
5- | Addition of host to cluster(with ram overcommit =1 and cpu overcommit >1) | add a host(which supports cpu overcommit but not ram) to cluster | 1- CS should add host to cluster |
|
|
|
|
|
|
|
| ||
5- | Addition of host to cluster(with cpu overcommit >1 and ramovercommit >1) | add a host(which supports cpu and ram overcommit) to cluster | 1-CS should add host to cluster |
|
|
|
|
|
|
|
| ||
6 | Addition of host to cluster(with ram overcommit >1 and cpu overcommit =1) | add a host(ram overcommit not supported,but cpu overcommit supported ) to cluster | 1- CS should not add host to cluster |
|
|
|
|
|
|
|
| ||
7 | Addition of host to cluster(with ram overcommit =1 and cpu overcommit >1) | add a host(cpu overcommit not supported but ram overcommit supported) to cluster | 1- CS should not add host to cluster |
|
|
|
|
|
|
|
| ||
6- | Change in cpu overcommit factor from 1 to x(>1). of cluster | If there is host does not support cpu overcommit | 1-CS should not allow change of overcommit factor |
|
|
|
|
|
|
|
| ||
7- | Change in ram overcommit factor from 1 to x(>1). of cluster | If there is host does not support ram overcommit | 1-CS should not allow change of overcommit factor |
|
|
|
|
|
|
|
| ||
8- | Change in cpu and ram overcommit factor from 1 to x(>1). of cluster | If there is host does not support cpu and ram overcommit | 1-CS should not allow change of overcommit factor |
|
|
|
|
|
|
|
| ||
9 | Change in ram cpu and ram overcommit factor from 1 to x(>1). of cluster | If all the host cluster support cpu and ram overcommit | 1-CS should allow change of overcommit factor |
|
|
|
|
|
|
|
| ||
10 | Change in ram overcommit factor from 1 to x(>1). of cluster | If all the host cluster support ram overcommit | 1-CS should allow change of overcommit factor |
|
|
|
|
|
|
|
| ||
11 | Change in cpu overcommit factor from 1 to x(>1). of cluster | If all the host cluster support cpu overcommit | 1-CS should allow change of overcommit factor |
|
|
|
|
|
|
|
| ||
| Addition of host to a cluster |
|
|
|
|
|
|
|
|
|
| ||
1-Login through UI |
|
|
|
|
|
|
|
|
| ||||
4 | 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 | 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 | 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 | ||
7 | 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 | ||
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 allow addition of host | P0 | Functional | Y | Y | Y | Y | N | N | ||
9 | 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 | ||
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 not allow addition of host | P0 | Functional | Y | Y | Y | Y | N | N | ||
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 | ||
12 | 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 |
|
|
|
|
|
|
|
|
| |||
13 | 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 | |||
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 | ||
15 |
| 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 |
| 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 | ||
|
|
|
|
|
|
|
|
|
|
| |||
| Overcommit factor conflict effect on host in cluster |
|
|
|
|
|
|
|
|
| |||
|
| 1-Login through UI |
|
|
|
|
|
|
|
|
| ||
17 | 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 | ||
18 | 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 | ||
19 | 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 | ||
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 | ||
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 | ||
22 | 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 | ||
23 | 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 | ||
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 | ||
25 | 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 |
|
|
|
|
|
|
|
|
| |||
26 | upgrade path | Pre upgrade steps | 1- Upgrade should be successful . |
| Upgrade | Y | Y | Y | Y | N | N | ||
| Effect of contention on vms |
|
|
|
|
|
|
|
|
|
| ||
27 | CPU contention | 1-Deploy a vm with SO which cause CPU contention | VM should be assign to CPU=(CPU define in SO/CPU overcommit factor) | P1 | Functional | Y | Y | Y | Y | N | N | ||
28 | RAM contention | 1- Deploy a vm with SO which cause RAM contention | VM should be assign 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="a43840f70091ecbc-d7f100dd-48374dd6-af01ad02-a397c0bf39e651c71ad143f2"><ac:plain-text-body><![CDATA[ | 29 | CPU and RAM contention | 1-Deploy a vm with SO which cause CPU and RAM contention | VM should be assign 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> |
30 | Dash board resource display |
|
|
|
|
|
| ||||||
31 |
| physical availability or logical(in case of overcommit) | yet to decide(https://issues.apache.org/jira/browse/CLOUDSTACK-1098) | P2 | Functional |
|
|
|
|
|
|