Page History

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

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

check cluster level settings for

cpu.overprovisioning.factor

mem.overprovisioning.factor

2- update overprovisioning  ratio using following API 

for cpu name=cpu.overprovisioning.factor

for memory name=mem=cpu.overprovisioning.factor

http://10.220.*.*:8096/client/api?command=updateConfiguration&clusterid=01d9a06d-f493-4764-88b0-5a093dfcb491&response=json&name=cpu.overprovisioning.factor&value=2

3-List cluster

1-cluster level setting should have both settings

2-using api mentioned 2 you shoul be able to change overprovisioning  factors

3-List cluster response should show overprovisioning  factors

P1

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

2

DB check

1-Logoin through UI
2-create a cluster and change overprovisioning.factor to x
3-check cluster_detail table

5-check user_vm_details table

1-There should be   attribute ,memoryOvercommitRatio  and value  for each cluster .

2-user_vm_details table should have entry for every vm  with cpu/mem.overprovisioning.factor

P1

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

  Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-1739

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

Pass

used capacity

(service offering of vm / overcommit it got deployed with) * new overcommit

(service offering of vm/overcommit value in user_vm_details table for that vm )*overCommit value in cluster details table for vm  cluster

Total capacity

===========

(cpu/mem).overprovisioning.factor*total actual capacity

1-calculate total capacity for cluster,pod,zone it should follow the  same formula

 Deploy VM in cluster

4

Deploy vm in a cluster

6

Deploy vm in a cluster with a service offering(
CPU ram=y)

1-Create a cluster with overcommit factor x
2- say total available CPU memory on host is z
3-deploy a vm N vms with service offering (CPUram=y) when  until z.x>=N.y

1- VM in step 3 should get deployed
  

P1

Functional

Y

Pass

Pass

https://issues.apache.org/jira/browse/CLOUDSTACK-1739

Pass(need some discussion )

5

Deploy VM in cluster with service offering(ram

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 memory on host is z
3-deploy a vm N vms with service offering (CPUram=y) when  until   z.x<N.x<y y

1- Deployment of vm in step 3 should fail.

P1

Functional

Y

Pass

Pass Block

Pass

8 6

Deploy vm in a cluster with overcommit factor x . and total available ram = M a service offering(
CPU=y)

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

Create a cluster with overcommit factor x
2- say total available CPU on host is z
3-deploy N vms with service offering (CPU=y) until  z.x>=N.y

1- VM in step 3 should get deployed

P1

Functional

Y

Pass

Pass

Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-1822

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 N vms with service offering (CPU=y) until z.x<N.y

1- Deployment of vm in step 3 should fail.

P1

Functional

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 Pass

Pass

10 9

Addition of host to cluster

1- Add add host which have overcommit capacity (with having licence) to a cluster
2-Add another host (with wich don't have overcommit capacity (no licence) to same cluster 3-Repeat step 1 and 2 with host(without licence)

1-step 2 should be successful 

P2

1-Should fail xen does not support mixed licensing

P2

Fuctional Functional

Y

Pass

N/A

N/A

11

weight

1-Deploy vms with different  service offerings

vm with different SO cpu speed (cpu speed*vcp ) should get different weight

P2

Functional

Y

Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-1646

 Pass

Pass

"overcommit ratio update " effect on existing and new  vms and capacity calculation

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

1-VMs deployed in step-3 should have entry in user_vm_detail with overcommit x 

12

  11

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

12 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

6  should fail

P1

Functional

Y

Pass

Pass

Pass

13 14

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

1-VM deployed in step 3 should not have any effect of step 6  should be successful

and an entry should be created in user_vm_Detail table with memory overcommit y

2-step 6  should be successful

P2

capacity calculation should be according  to test case 3 "capacity Calculation "

P2

Functional

Y

Pass

Block

Pass

14 15

5-when y>x (For CPU)
6-Deploy a  vm.

1-VM deployed in step 3 should not have any effect of step 6  should be successfuland an entry should be created in user_vm_Detail table with cpu overcommit y

2-step 6  capacity calculation should be successful according to test case 3 "capacity Calculation "

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

1-VMs deployed in step-3 should have entry in user_vm_detail with overcommit x 

15 16

Reboot

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

1-VM should use previous overcommit ratio(x),should come up without failure Overcommit value should not get changed  for the vms in user vm details table vm

P2

Functional

Y

Pass

Pass

Pass

16 17

Reboot

4-Reboot all the vms in deployed in step 2 when x<y

1-VM should use previous overcommit ratio(x),should come up without failure.
P2 Overcommit value should not get changed  for the  vms in user vm details table

P2

Functional

Y

Pass

Pass

Pass

17 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(y),
2Overcommit value should be changed to y for the  vms in user vm details table
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

Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-1695

Pass 

18 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(y). Overcommit value should be changed to y for the  vms in user vm details table

2-all VM should come up without failure

P2

Functional

Y

Pass

Pass

Pass

19 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(y), Overcommit value should be changed to y for the  vms in user vm details table
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

Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-1695

Pass 

20 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(y). Overcommit value should be changed to y for the  vms in user vm details table
2-all VM should come up without failure

P2

Functional

Y

Pass

Pass

Pass

21 22

(manage/unmanage-Disable/enable  cluster)

1-Create a cluster with overcommit ratio x
2-unmanage-manage cluster <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="

1" ac:macro-id="18b86292-d0d1-4acf-bab9-ca0877acd761"><ac:plain-text-body><![CDATA[

1-Overcommit ratio should not change

-Overcommit value should not get changed  for the  vms in user vm details table

P2

Functional

Y

Fail Pass

[https://issues.apache.org/jira/browse/CLOUDSTACK-1534
]]></ac:plain-text-body></ac:structured-macro>
]
153

Pass

Pass

23

22

upgrade path

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

3-set cpu overcommit  to x

4- set vmware.reserve.(mem/cpu) to true

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 and global level settings it should list

(cpu/mem).overcommit.factor and vmware.reserve.(cpu/mem) with same values as before upgrade
3-Check cluster detail table it should have some attribute to store overcommit factor for cluster.
3 4-in postupgrade step-2 vm should get deployed successfully .
4 5- In postupgrade step-3 vm deployment should fail. 

Upgrade

Y

6-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

Block

Waiting for new system vm template. 

23 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

24 25

Number of max VM can be deployed (RAM overcommit factor x, actula 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

25

Migrate vm from one cluster to another

vm should be able to migrate in any cluster ,having required resources available, irrespective of overcommit factor .

P1

Functional(hold)

Y

26

Dash board display for multi cluster environment

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

https://issues.apache.org/jira/browse/CLOUDSTACK-1640

Add xen , vmware, kvm clusters

2- set (cpu/meme) overpovisioning to x for xen cluster and check zone total capacity

3- set (cpu/mem)overpovisioning to x for kvm cluster and check zone total capacity

4- set (cpu/mem)overpovisioning to x for vmware cluster and check zone total capacity

1-Total  capacity should be[ x.(xen cluster capacity)+kvm cluster capacity+vmware cluster capacity]

2-In step 1-Total  capacity should be[ x.(kvm cluster capacity)+xen cluster capacity+vmware cluster capacity]

3-in step 4-Total  capacity should be [x.(vmware cluster capacity)+kvm cluster capacity+xen cluster capacity]

P2

Functional

Y

Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-1640

Fail

Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-1809

27

overcommit ratio

27

overcommit ratio <1

1-Craete a cluster with overcommit ratio x
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="680a876e-6e44-4f30-9a43-a4d87fdc2a1d"><ac:plain-text-body><![CDATA[2-Change overcommit ratio to <1

1-Cs should not allow to set overcommit ratio <1

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

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
https://issues.apache.org/jira/browse/CLOUDSTACK-3187

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-1528
]]></ac:plain-text-body></ac:structured-macro>
jira/browse/CLOUDSTACK-3365

Fail 

Fail

28 30

cluster.cpu.allocatedoverpovisioning .capacity.disablethreshold factor

set cluster. cpu.allocated.capacity.disablethreshold
overpovisioning .factor to some value say .85

1-Should be calculated based on overcommit ratio Expected to  be there in Global settings

P2

Functional

Y

 Pass

https://issues.apache.org/jira/browse/CLOUDSTACK-17041705

 Pass

Pass

29 31

cluster.cpumemory.allocated.capacity.notificationThreshold disablethreshold

set
cluster.cpumemory.allocated.capacity.notificationThreshold disablethreshold
to some value(say 0.5)

1-should be calculated based on overcommit ratio overcommited memory

P2

Functional functional

Y

Pass

https://issues.apache.org/jira/browse/CLOUDSTACK-1622

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

30

cpu.overpovisioning .factor

set cpu.overpovisioning .factor to some value

1-Should not be there in Global settings

P2

Functional

Y

Fail

https://issues.apache.org/jira/browse/CLOUDSTACK-17053365

 Block

Fail

  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

Fail

vmware.reserver.cpu

1-set cpu.overpovisioning .factor  to x>1

2- set vmware.reserver.cpu to false and deploy vm

3-set vmware.reserver.cpu to true and deploy vm

1-In step 2 vm should get deployed and no cpu resource should get reserved for the vm

2-in step 3 vm should get deployed and  cpu =cpu in so/x  resource should get reserved for the vm

set cluster.memory.allocated.capacity.notificationthreshold
to some value(say 0.5)

1-should be calculated based on overcommited memory

1-set cpu.overpovisioning .factor  to x>1

2- set vmware.reserver.mem to false and deploy vm

1-In step 2 vm should get deployed and no mem resource should get reserved for the vm