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

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

2 3

DB check

1-Logoin through UI
2-create a cluster with overcommit and change overprovisioning.factor to x
3-Login to DB
4-check cluster detail check cluster_detail table

5-check user_vm_details table

1-There should be some be   attribute ,which  represent overcommit factor and should have store overcommit factor for the clusters .
memoryOvercommitRatio  and value  for each cluster .

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

P1 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

used capacity

 ( service offering of vm / overcommit it got deployed with) * new cpu/mem 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

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

4

Where host cpu overcommit capabilities<cluster cpu overcommit  factore and
RAM overcommit capabilities < cluster RAM overcommit factore

1-CS should not allow addition of host

P0

Functional

Y

Y

Y

Y

N

N

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

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

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

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

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

11

weight

1-Deploy vms with different  service offerings

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

P2

Functional

Y

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

5

Where host cpu overcommit capabilities<cluster cpu overcommit  factore and
RAM overcommit capabilities > cluster RAM overcommit factore

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
RAM overcommit capabilities =cluster RAM overcommit factore

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
RAM overcommit capabilities < cluster RAM overcommit factore

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
RAM overcommit capabilities > cluster RAM overcommit factore

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
RAM overcommit capabilities = cluster RAM overcommit factore

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
RAM overcommit capabilities < cluster RAM overcommit factore

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
RAM overcommit capabilities >cluster RAM overcommit factore

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
RAM overcommit capabilities =cluster RAM overcommit factore

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
2-Create a cluster with overcommit ratio x
3-Deploy a vm 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

  13

5-when y<x and there is no(less than required) resource left in cluster according to new overcommit ratio 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  for both CPU and RAM
fail  

P1 P0

Functional

Y

Y

Y

Y

N

N

14

13

5-when y<x and there is enough resource left in cluster according to new overcommit ratio (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 for both CPU and RAM
6  should fail

P1 P0

Functional

Y

Y

Y

Y

N

N

15 14

5-when y>x and there is enough resource left in cluster according to new overcommit ratio (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 for both CPU and RAM
capacity calculation should be according  to test case 3 "capacity Calculation "

P2 P0

Functional

Y

Y

Y

Y

N

N

16 15

5-when y>x and there is not enouh resource left in cluster according to new overcommit ratio (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  should fail for both CPU and RAM

P0

Functional

Y

Y

Y

Y

N

N

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

P1

Functional

Y

 VM Life cycle

Overcommit factor  conflict effect on host in cluster

17

where host cpu overcommit capabilities < updated cpu overcommit factor and
host ram overcommit capabilities < updated ram overcommit factor

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
host ram overcommit capabilities > updated ram overcommit factor

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
host ram overcommit capabilities = updated ram overcommit factor

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
host ram overcommit capabilities < updated ram overcommit factor

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
host ram overcommit capabilities > updated ram overcommit factor

1-host should remain in cluster, and should  be available for vm deployment

P0

Functional

Y

Y

Y

Y

N

N

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

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

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

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

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

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

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

22

where host cpu overcommit capabilities > updated cpu overcommit factor and
host ram overcommit capabilities = updated ram overcommit factor

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
host ram overcommit capabilities < updated ram overcommit factor

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
host ram overcommit capabilities > updated ram overcommit factor

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
host ram overcommit capabilities = updated ram overcommit factor

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

26 23

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.
2(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. 
6-in step 5 ,vm should  get max min resource based on new overcommit ratio.

Upgrade

Y

Y

Y

Y

N

N

Effect of contention on vms

27

24

Number of max VM can be deployed (CPU overcommit factor x, actual cpu C) in case enough RAM  available. 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)

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 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="57914f59-f629-4bc1-9730-618df18e98c0"><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>

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

26

Dash board display for multi cluster environment

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

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

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

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

30

cpu.overpovisioning .factor

set cpu.overpovisioning .factor to some value

1-Expected to  be there in Global settings

P2

Functional

Y

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

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

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

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

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