Over commit CPU and Memory

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

1

UI/API check

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

Y

Pass

Pass

Pass

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

Y

Pass

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/meme).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 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 N vms with service offering (ram=y) 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 =y)

1-Create a cluster with overcommit factor x
2- say total available memory on host is z
3-deploy N vms with service offering (ram=y) until   z.x<N.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 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

Y

Pass

Pass

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

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

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

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

1-step 6  should fail  

P1

Functional

Y

Pass

Block

Pass

13

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

1-step 6  should fail

P1

Functional

Y

Pass

Pass

Pass

14

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

1-step 6  should be successful

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

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

P2

Functional

Y

Pass

Block

Pass

15

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

1-step 6  should be successfuland an entry should be created in user_vm_Detail table with cpu overcommit y

2-capacity calculation should be 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 

16

Reboot

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

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

P2

Functional

Y

Pass

Pass

Pass

17

Reboot

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

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

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

19

stop/start

4-Stop and start all the vms in deployed in step 2 when x<y

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

20

destroy/restore ->start

4-Destroy and restore and start  all the vms in deployed in step 2 when x>y

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

21

destroy/restore ->start

1-destroy/restore->start  all the vms in deployed in step 2 when x<y

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

22

(manage/unmanage-Disable/enable  cluster)

1-Create a cluster with overcommit ratio x
2-unmanage-manage cluster

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

P2

Functional

Y

Pass

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

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

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

Fail

Fail

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

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

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

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

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

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

Block

Fail