Versions Compared

Old Version 52

changes.mady.by.user prashant kumar mishra

Saved on

compared with

New Version 53

changes.mady.by.user prashant kumar mishra

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

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

 

 

 

 

 

 

 

 

 

 

Test Case ID

Test Case Name

Steps

Expected Result

Priority
(P0 | P1)

Test Case Type
(Sanity/Functional/Upgrade/Performance)

Automatable(Y/N)

VMWARE(Y/N)

KVM(Y/N)

XEN(Y/N)

OVM(Y/N)

BAREMETAL(Y/N)

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

 

 

 

 

 

 

Deploy vm in a cluster with ram overcommit factor 2x

1-deploy vm with ram= x
2- deploy another VM with ram<=x

1- VM in step 1 should get deployed
2-VM in step 2 should also get deployed

 

 

 

 

 

 

 

 

 

Deploy VM in cluster with ram overcommit factor 2x

1-deploy vm with ram= x
2- deploy another VM with ram>x

1- VM in step 1 should get deployed
2-VM in step 2 should not  get deployed

 

 

 

 

 

 

 

 

 

Deploy vm in a cluster with cpu overcommit factor 2x

1-deploy vm with cpu= x
2- deploy another VM with cpu<=x

1- VM in step 1 should get deployed
2-VM in step 2 should also get deployed

 

 

 

 

 

 

 

 

 

Deploy vm in a cluster with cpu overcommit factor 2x

1-deploy vm with cpu= x
2- deploy another VM with cpu >x

1- VM in step 1 should get deployed
2-VM in step 2 should not  get deployed

 

 

 

 

 

 

 

 

 

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

1-CS will choose a value in y/x to y such that total required ram will be < M.

 

 

 

 

 

 

 

 

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

 

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

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

Number of max VM can be deployed (RAM overcommit factor x, actula ram M) in case enough CPUs are available.

1- Deploy a vm with a SO where ram=y ,limit(y/x ,y)

number of vm must be limited by n*y/x<M (nummber of vm *lower value of ram < total memory in cluster)

P1

Functional

Y

Y

Y

Y

N

N

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7b76ca56aa047e8b-cd5557c8-452b4524-9c5fa705-ce351278fd4842deeea8fa89"><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>


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