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

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

Overcommit factor  conflict effect on vms

1-Login Through UI
2-Create a cluster with overcommit ratio x
3-Deploy a vm
4-Change overcommit ratio to y

13

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

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

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

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

P0

Functional

Y

Y

Y

Y

N

N

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

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

Upgrade from 4.0 to 4.1

26

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

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. 

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="eef01c126b912df6-c80da330-420947ec-838cb69e-bbb48d8128497bd74541454a"><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