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

Compare with Current View Page History

« Previous Version 28 Next »

 

Following hypervisor support this feature
  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)

 

UI/API check

1-Add cluster using  API addCluster

add cluster API should have new parameters  cpuovercommitratio and ramovercommitratio

 

 

 

 

 

 

 

 

 

UI/API check

1- Fire API UpdateOvercommitRatio with parameter cpuovercommitratio,ramovercommitratio.

response should contain " details of the updated cluster along with the overcommit ratios"

 

 

 

 

 

 

 

 

 

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 .

 

 

 

 

 

 

 

 

 

Addition of host to a cluster

 

 

 

 

 

 

 

 

 

 

 

1-Login through UI
2-Add a cluster with
overcommit  factor         resource
     x                              CPU
     y                              RAM.

3-Prepare a Host having
overcommit capability     Resource
      c                              CPU
      r                               RAM

 

 

 

 

 

 

 

 

 

 

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

N

N

 

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

N

N

 

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

N

N

 

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

N

N

 

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

N

N

 

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

N

N

 

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

N

N

 

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

N

N

 

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 host

P0

Functinal

 

Y

Y

Y

N

N

 

Overcommit factor  conflict effect on vms

 

 

 

 

 

 

 

 

 

 

 



 

1-Already deployed vm should not have any effect
2-Only vm deployed here after should get deployed based on new Overcommit factor.

P0

Functional

 

Y

Y

Y

N

N

 

Overcommit factor  conflict effect on host in cluster

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

where host cpu overcommit cpabilities < new cpu overcommit factor


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

P0

Functional

 

Y

Y

Y

N

N

 

where host cpu overcommit cpabilities >= new cpu overcommit factor


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

P0

Functional

 

Y

Y

Y

N

N

 

where host ram overcommit cpabilities < new ram overcommit factor

 

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

P0

Functional

 

Y

Y

Y

N

N

 

where host ram overcommit cpabilities >= new ram overcommit factor

 

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

P0

Functional

 

Y

Y

Y

N

N

 

where host cpu and ram overcommit cpabilities < new  cpu and ram overcommit factor

 

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

P0

Functional

 

Y

Y

Y

N

N

 

where host CPU and RAM overcommit cpabilities >= new cpu and ram overcommit factor

 

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

P0

Functional

 

Y

Y

Y

N

N

 

Upgrade from 4.0 to 4.1

 

 

 

 

 

 

 

 

 

 

 

upgrade path

1-Disable overcommit feature and do normal upgrade
2-Manually enable feature.

1- Upgrade should be successful .
2-feature should be successfully enable.

 

 

 

 

 

 

 

 

 

Effect of contention on vms

 

 

 

 

 

 

 

 

 

 

 

CPU contention

 

VM should get assigne to CPU=(CPU define in SO/CPU overcommit factor)

P1

Functional

 

 

 

 

 

 

 

RAM contention

 

VM should get assigne to RAM=(RAM define in SO/RAM overcommit factor)

P1

Functional

 

 

 

 

 

 

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7389a8da-022f-419b-93ca-e812b5b4d2f6"><ac:plain-text-body><![CDATA[

 

CPU and RAM contention

 

VM should get assigne to (CPU/RAM)=[(CPU/RAM) define in SO/(CPU/RAM) overcommit factor]

P1

Functional

 

 

 

 

 

 

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

 

Dash board resource display

physical availability or logical(in case of overcommit)

yet to decide

P2

Functional

 

 

 

 

 

 
  • No labels