Page History

This feature is implemented for following hypervisor
1-VMWARE
2-KVM
3-XEN

Test Case ID
Test Case Name
Steps
Expected Result
Priority
(P1 | P2|P3)
Test Case Type
(Sanity/Functional/Upgrade/Performance)
Automatable
(Y/N)
XEN
(Pass|Fail)
Comment
(XEN)
KVM
(Pass|Fail) Comment
(KVM)
VMWARE
(Pass|Fail) Comment
(VMWARE)
1 UI/API check
1-Add cluster using API addCluster
add cluster API should have new parameters cpuovercommitratio and memoryovercommitratio P1 Y Pass Pass Pass
2 UI/API check
1- update overcommit ratio using API updateCluster with parameter cpuovercommitratio,memoryovercommitratio. response should contain " details of the updated cluster along with the overcommit ratios" P1 Y Pass Pass Pass
3 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 attribute ,name,value for each cluster .
P1 Y Pass Pass Pass

Deploy VM in cluster

4 Deploy vm in a cluster with a service offering(
ram=y)
1-Create a cluster with overcommit factor x
2- say total available memory on host is z
3-deploy a vm with service offering (ram=y) when z.x>=y
1- VM in step 3 should get deployed

P1 Functional Y Pass Pass

https://issues.apache.org/jira/browse/CLOUDSTACK-1739^{Image Added} Pass(need some discussion )
https://issues.apache.org/jira/browse/CLOUDSTACK-3415^{Image Added}
5 Deploy VM in cluster with service offering(ram =y)
1-Create a cluster with overcommit factor x
2- say total available memory on host is z
3-deploy a vm with service offering (ram=y) when z.x<y 1- Deployment of vm in step 3 should fail.
P1 Functional Y Pass Block Pass
6 Deploy vm in a cluster with a service offering(
CPU=y) 1-Create a cluster with overcommit factor x
2- say total available CPU on host is z
3-deploy a vm with service offering (CPU=y) when z.x>=y 1- VM in step 3 should get deployed P1 Functional Y Pass

Pass Fail https://issues.apache.org/jira/browse/CLOUDSTACK-1822^{Image Added}
7 Deploy vm in a cluster with a service offering(
CPU=y) 1-Create a cluster with overcommit factor x
2- say total available CPU on host is z
3-deploy a vm with service offering (CPU=y) when z.x<y 1- Deployment of vm in step 3 should fail. P1 Functional Y Pass Pass Pass
8 Deploy vm in cluster with overcommit factor x . and total available ram = M
1-Deploy vm with aSO where ram=y GB
2-max and min will be y GB and y/x GB
3-Deploy vms such sum of all y>M

1-CS will choose a value in y/x to y such that total required ram will be <= M.
P1 Functional Y Pass Block *Pass
9 Addition of host to cluster
1- add host which have overcommit capacity (having licence)
2-Add another host wich don't have overcommit capacity (no licence)
1-Should fail xen does not support mixed licensing
P2 Fuctional Y Pass N/A
N/A
10 Addition of host to cluster
1-Add host(with licence) to a cluster
2-Add host (with licence) to same cluster
3-Repeat step 1 and 2 with host(without licence)

1-step 2 should be successful
P2 Functional
Y
Pass N/A N/A
11 weight
1-Deploy vms with different service offerings
vm with different cpu speed (cpu speed*vcp ) should get different weight
P2
Functional
Y
Fail
https://issues.apache.org/jira/browse/CLOUDSTACK-1646^{Image Added} Pass Pass

"overcommit ratio update " effect on existing and new vms

1-Login Through UI
2-Create a cluster with overcommit ratio x
3-Deploy vms so that no resource are left in cluster
4-Change overcommit ratio to y

12

5-when y<x (for Memory)
6-Deploy a vm.

1-VM deployed in step-3 should not have any effect of y
2-step 6 should fail
P1 Functional Y Pass Block Pass
13
5-when y<x (for CPU)
6-Deploy a vm. 1-VM deployed in step-3 should not have any effect of y
2-step 6 should fail
P1
Functional Y Pass Pass Pass
14
5-when y>x (for Memory)
6-Deploy a vm. 1-VM deployed in step-3 should not have any effect of y
2-step 6 should be successful
P2
Functional Y Pass Block Pass
15
5-when y>x (For CPU)
6-Deploy a vm. 1-VM deployed in step-3 should not have any effect of y
2-step 6 should be successful
P1
Functional Y Pass Pass Pass

VM Life cycle

1-set cluster overcommit ratio x
2-Deploy some vm such that no resources are available on current host
3-change overcommit ratio to y

16 Reboot 4-Reboot all the vms , deployed in step 2 when x>y

1-VM should use previous overcommit ratio,should come up without failure

P2 Functional Y Pass Pass
Pass

17 Reboot 4-Reboot all the vms in deployed in step 2 when x<y 1-VM should use previous overcommit ratio,should come up without failure.
P2 Functional Y Pass Pass Pass
18 stop/start
4-Stop and start all the vms in deployed in step 2 when x>y 1-VM should use current overcommit ratio,
2-If Summation of SO/Overcommit ratio for all vms< available actual memory and service ,
a-then all vm should come up without failure
b-else only few vms come up which satisfy above condition
P2 Functional Y Pass for Memory
Failed for CPU
https://issues.apache.org/jira/browse/CLOUDSTACK-1695^{Image Added} Fail https://issues.apache.org/jira/browse/CLOUDSTACK-1695^{Image Added}
Pass
19
stop/start 4-Stop and start all the vms in deployed in step 2 when x<y 1-VM should use current overcommit ratio.
2-all VM should come up without failure
P2
Functional
Y
Pass
Pass Pass
20
destroy/restore ->start
4-Destroy and restore and start all the vms in deployed in step 2 when x>y 1-VM should use current overcommit ratio,
2-If Summation of SO/Overcommit ratio for all vms< available actual memory and service ,
a-then all vm should come up without failure
b-else only few vms come up which satisfy above condition P2
Functional
Y
Pass for memory
Failed for CPU
https://issues.apache.org/jira/browse/CLOUDSTACK-1695^{Image Added} Fail https://issues.apache.org/jira/browse/CLOUDSTACK-1695^{Image Added} Pass
21
destroy/restore ->start 1-destroy/restore->start all the vms in deployed in step 2 when x<y 1-VM should use current overcommit ratio.
2-all VM should come up without failure
P2 Functional
Y Pass Pass Pass
22 (manage/unmanage-Disable/enable cluster)
1-Create a cluster with overcommit ratio x
2-unmanage-manage cluster

1-Overcommit ratio should not change
P2 Functional
Y
Pass
https://issues.apache.org/jira/browse/CLOUDSTACK-153^{Image Added}
Pass
Pass

23
upgrade path
Pre upgrade steps
1-Deploy some vms
2-Have some snapshot and template

Post upgrade steps
1-add cluster with overcommit factor x
2-Deploy a vm where required resource for vm <= resource available in cluster according to overcommit factor
3-Deploy a vm where required resource for vm > resource available in cluster according to overcommit factor
4-stop vms and change overcommit ratio .
5-Start vms .

1- Upgrade should be successful .
2-Check cluster detail table it should have some attribute to store overcommit factor for cluster.
3-in postupgrade step-2 vm should get deployed successfully .
4- In postupgrade step-3 vm deployment should fail.
5-in step 5 ,vm should get max min resource based on new overcommit ratio. Upgrade Y Pass (RAM)
CPU testing is blocked because of issue https://issues.apache.org/jira/browse/CLOUDSTACK-1695^{Image Added} Block Waiting for new system vm template.

24
Number of max VM can be deployed (CPU overcommit factor x, actual cpu C) in case enough RAM available. 1- Deploy a vm with a SO where cpu=y .
number of vm must be limited by n*y*vcpu/x<C (nummber of vm *lower value of ram*vcpu < total cpu in cluster) P2 Functional Y Pass Pass *Pass
25
Number of max VM can be deployed (RAM overcommit factor x, actual ram M) if enough CPUs are available.
1- Deploy vms with a SO where ram=y ,
number of vm must be limited by n*y/x<M (nummber of vm *lower value of ram < total available memory on current host)
P2 Functional Y Pass Block Pass

26
Dash board display

1-set overcommit ratio to x
2-Deploy some vms so that no resource left in cluster
3-Check dashboard display
1-Overcommited values should get displayed at zone/pod/cluster level with % of use based on overcommited values P2
Functional Y Fail https://issues.apache.org/jira/browse/CLOUDSTACK-1640^{Image Added} Fail Fail https://issues.apache.org/jira/browse/CLOUDSTACK-1809^{Image Added}
27
overcommit ratio <1
1-Craete a cluster with overcommit ratio x
2-Change overcommit ratio to <1
1-Cs should not allow to set overcommit ratio <1
P3
Functional
Y
Fail https://issues.apache.org/jira/browse/CLOUDSTACK-1528^{Image Added}

Fail Fail
28
cluster.cpu.allocated.capacity.disablethreshold set cluster.cpu.allocated.capacity.disablethreshold
to some value say .85
1-Should be calculated based on overcommit ratio P2
Functional
Y
Pass
https://issues.apache.org/jira/browse/CLOUDSTACK-1704^{Image Added} https://issues.apache.org/jira/browse/CLOUDSTACK-3187^{Image Added}
Pass
Pass

29
cluster.cpu.allocated.capacity.notificationThreshold
set cluster.cpu.allocated.capacity.notificationThreshold
to some value
1-should be calculated based on overcommit ratio
P2
Functional
Y
Fail https://issues.apache.org/jira/browse/CLOUDSTACK-3365^{Image Added} Fail Fail
30
cpu.overpovisioning .factor
set cpu.overpovisioning .factor to some value
1-Expected to be there in Global settings
P2
Functional
Y
Pass
https://issues.apache.org/jira/browse/CLOUDSTACK-1705^{Image Added}
Pass
Pass

31
cluster.memory.allocated.capacity.disablethreshold
set
cluster.memory.allocated.capacity.disablethreshold
to some value(say 0.5)
1-should be calculated based on overcommited memory
P2
functional
Y
Pass
https://issues.apache.org/jira/browse/CLOUDSTACK-1622^{Image Added} Pass
Pass

32
cluster.memory.allocated.capacity.notificationthreshold set cluster.memory.allocated.capacity.notificationthreshold
to some value(say 0.5) 1-should be calculated based on overcommited memory P2
Functional Y
Fail https://issues.apache.org/jira/browse/CLOUDSTACK-3365^{Image Added}
Block Fail