You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 70 Next »

 

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  store overcommit factor for the already existing clusters .

P0

 

Y

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4

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

P0

Functional

Y

Y

Y

Y

N

N

5

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

P0

Functional

Y

Y

Y

Y

N

N

6

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

P0

Functional

Y

Y

Y

Y

N

N

7

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

P0

Functional

Y

Y

Y

Y

N

N

8

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

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

P0

Functional

Y

Y

Y

Y

N

N

 

 

 

 

 

 

 

 

 

 

 

 

9

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

Functional

Y

Y

Y

Y

N

N

10

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

P0

Functional

Y

Y

Y

Y

N

N

11

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

P0

Functional

Y

Y

Y

Y

N

N

12

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

P0

Functional

Y

Y

Y

Y

N

N

13

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

P0

Functional

Y

Y

Y

Y

N

N

 

 

 

 

 

 

 

 

 

 

 

 

14

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

P0

Functional

Y

Y

Y

Y

N

N

15

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

P0

Functional

Y

Y

Y

Y

N

N

16

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

P0

Functional

Y

Y

Y

Y

N

N

17

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

P0

Functional

Y

Y

Y

Y

N

N

18

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

P0

Functional

Y

Y

Y

Y

N

N

19

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

P0

Functional

Y

Y

Y

Y

N

N

 

"overcommit factor update " effect on vm

 

 

 

 

 

 

 

 

 

 


 

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

 

 

 

 

 

 

 

 

 

20



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

21

 

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

22

 

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

23

 

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

 

 

 

 

 

 

 

 

 

 

 

 

24

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

 

 

 

 

 

 

 

 

 

 

 

 

25

Number of max VM can be deployed (CPU overcommit factor x, actula 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/x<C (nummber of vm *lower value of ram < total cpu in cluster)

P1

Functional

Y

Y

Y

Y

N

N

26

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

 

 

 

 

 

 

 

 

 

 

 

 

27

Migrate vm from one cluster to another


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

P0

Functional

Y

Y

Y

Y

N

N

 

 

 

 

 

 

 

 

 

 

 

 

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1a6476e3-faf2-4d4e-96c5-d7d74b2c09b3"><ac:plain-text-body><![CDATA[

28

Dash board display

 

yet to decide [https://issues.apache.org/jira/browse/CLOUDSTACK-1098]

 

 

 

 

 

 

 

 

]]></ac:plain-text-body></ac:structured-macro>
  • No labels