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

Compare with Current View Page History

« Previous Version 6 Next »

Please find the  rough draft on Better VM Sync Test Plan below:(VMware/Kvm/Xen)

VMsync-VMware.xlsx

SNO

TestCase_Name

Steps

Extected results

Priority

Type(functional/Sanity/negative)

Status

Hypervisor

1

Stop a VM from vcenter/xencenter/datacenter

Steps:
1. Deploy A VM from CS
2.Stop the deployed VM from Vcenter/xencenter/datacenter

Vm  should be stopped successfully and VM sync should update the VMstate in CS properly
.i.e on both sides(bothh hypervisor & CS) ,VM  should be stop state.

P1

Functional

 

Vmware/KVM/Xen

2

Stop CS HA  enabled VM

Steps:
1. Deploy A HA enabled VM from CS
2.Stop the deployed VM from Vcenter

Vm  should be stopped successfully and VM sync should update the VMstate in CS properly
.i.e on both sides ,VM  should be stop state.

P1

Functional

 

Vmware/KVM/Xen

3

Stop a VM from CS

Steps:
1. Deploy A VM from CS
2.Stop the deployed VM from CS

Vm  should be stopped successfully and VM sync should update the VMstate in CS properly
.i.e on both sides ,VM  should be stop state.

P2

Functional

 

Vmware/KVM/Xen

4

Stop &start VM from CS

Steps:
1. Deploy A VM from CS
2.Stop & start the deployed VM from CS

Vm  should be stopped&started successfully and VM sync should update the VMstate in CS properly
.i.e on both sides ,VM  should be start state.

P1

Functional

 

Vmware/KVM/Xen

5

stop &start VM from  vcenter/xencenter/datacenter

Steps:
1. Deploy A VM from CS
2.Stop & start the deployed VM from Vcenter

Vm  should be stopped &started successfully and VM sync should update the VMstate in CS properly
.i.e on both sides ,VM  should be in start  state.

P1

Functional/Sanity

 

Vmware/KVM/Xen

6

Stop a Vm from CS and start a VM from vcenter/xencenter/datacenter

Steps:
1. Deploy A VM from CS
2.Stop  deployed VM from CS
3.start  the above VM from Vcenter

Vm  should be stopped &started successfully and CS VM sync should update the VMstate in CS properly
.i.e on both sides ,VM  should be in start  state.

P1

Functional

 

Vmware/KVM/Xen

7

Stop the system VMs from vcenter/xencenter/datacenter

1.Make sure system Vm and running in the setup.
2.Stop the system Vms

System vms will be stopped successfully and  will start again by the CS  and system Vms will

P2

Functional

 

Vmware/KVM/Xen

8

Stop and start system VM from vcenter

1.Make sure system Vm and running in the setup.
2.Stop and start the system Vms

System vms will be stopped  and started successfully

P1

Functional

 

Vmware/KVM/Xen

9

Stop and start router VM from vcenter/xencenter/datacenter

1.Make sure router Vm  running in the setup.
2.Stop and start the router Vms

router vms will be stopped and stared successfully.

P1

Functional

 

Vmware/KVM/Xen

10

stop& start a VM when current host resources are full

1. Deploy A VM from CS
2.Stop  deployed VM from CS
3.make sure current Host 's resources are full
4.start the VM

VM  should be stopped successfully and when we start it should start on another host .CS should  sync and update the state properly.I.e Vm should be up and runing

P1

Functional

 

Vmware/KVM/Xen

11

stop& start a system VM when current host resources are full

1.Make sure system Vms Up and running in the setup.
2.Stop the system Vms
3.make sure the current host resource are full

when current host resources are full ,System Vms should start on anoher host and state should be updated correctly.

P1

Functional

 

Vmware/KVM/Xen

12

stop& start  router VM when current host resources are full

1.Make sure system Vms Up and running in the setup.
2.Stop the system Vms
3.make sure the current host resource are full
4.start the router Vm

when current host resources are full ,System Vms should start on anoher host and state should be updated correctly.

 

Functional

 

Vmware/KVM/Xen

13

reboot VM from CS

Steps:
1. Deploy A VM from CS
2.reboot the VM from CS

Vm  should be rebooted successfully and VM sync should update the VMstate in CS properly
.i.e on both sides ,VM  should be running  state.

P2

Functional

 

Vmware/KVM/Xen

14

reboot VM from vcenter

Steps:
1. Deploy A VM from CS
2.reboot the VM from Vcenter

Vm  should be rebooted successfully and VM sync should update the VMstate in CS properly
.i.e on both sides ,VM  should be running  state.

P1

Functional

 

Vmware/KVM/Xen

15

migrate a VM and stop VM

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.stop the VM

migrated VM should stop successfully and VM sync should update the VMstate in CS properly

P1

Functional

 

Vmware/KVM/Xen

16

migrate a VM and stop &start VM

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.stop the VM and start the VM

migrated VM should stop &start successfully and VM sync should update the VMstate in CS properly

P1

Functional

 

Vmware/KVM/Xen

17

migrate a VM and reboot VM

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.reboot the VM

migrated VM should reboot successfully and VM sync should update the VMstate in CS properly

P1

Functional

 

Vmware/KVM/Xen

18

migrate a VM and reset a VM

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.reset the VM

migrated VM should reset successfully and VM sync should update the VMstate in CS properly

P1

Functional

 

Vmware/KVM/Xen

19

migrate a VM and destroy and restore

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.destroy and restore the VM

VM should be in stopped state

P2

Functional

 

Vmware/KVM/Xen

20

migrate a VM and stop a VM CS &start a VM from vcneter

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.stop  a VM from CS and start a VM   from vcenter.

VM should be in start state

P1

Functional

 

Vmware/KVM/Xen

21

migrate a VM and reboot VM from vcneter

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.reboot the VM from vcenter

migrated VM should reboot successfully and VM sync should update the VMstate in CS properly

P1

Functional/sanity

 

Vmware/KVM/Xen

22

deploy a VM in stopped state and start a VM

Steps:
1. Deploy A VM  in stopped state
2.start the VM

VM should be started successfully and state shoulb be up and running

P1

Functional

 

Vmware/KVM/Xen

23

deployed a VM in stopped stated and put host in maintenance

Steps:
1. Deploy A VM  in stopped state
2.Put host in maintenenanc mode

Vm should be in stop state  only

P2

Functional

 

Vmware/KVM/Xen

24

make cluster as unmnaged  to manage

Steps:
1.make sure few VM s are running and few Vms are in stoped state in the  setup
2.make cluster as unmanaged
3.make cluster as managed

VM sync should update the VMstate in CS properly,CS VM status should sync with hypervisor Vm state

P1

Functional

 

Vmware/KVM/Xen

25

stop few VM from vcenter/xencenter/datacenter and make cluster as managed

Steps:
1.make sure few VM s are running and few Vms are in stoped state in the  setup
2.make cluster as unmanaged
3. stop few VM from vcenter
4. Then make cluster as managed

VM sync should update the VMstate in CS properly,CS VM status should sync with hypervisor Vm state

P1

Functional/sanity

 

Vmware/KVM/Xen

26

migrate few vms from vcneter and make cluster as managed

Steps:
1.make sure few VM s are running and few Vms are in stoped state in the  setup
2.make cluster as unmanaged
3. migrate few VM from vcenter
4. Then make cluster as managed

VM sync should update the VMstate in CS properly

P1

Functional

 

Vmware/KVM/Xen

27

deploy Vms and put host in maintenance

Steps:
1. Deploy few  VMs on cluster having 2 host
2.put the current host in maintenance mode

all the VMs(nonHA) in stopped state 

P1

Functioanl

 

Vmware/KVM/Xen

29

deploy HA enabled VMs and put host in maintenance

Steps:
1. Deploy few  HA enabled VMs on cluster having 2 host
2.put the current host in maintenance mode

All the HA enabled VMs moved to another Host  ,CS VM status should sync with hypervisor Vm state

P1

Functional

 

Vmware/KVM/Xen

30

Shutdown  VM form console

1.deploy a VM
2.login to VM console
3.shutdown the VM from  VM cosole

VM sync should update the VMstate in CS properly and VM shoud be shutdown state

P2

Functional

 

Vmware/KVM/Xen

31

Poweroff VM  from vcenter/xencenter/datacenter

1.deploy a VM  from CS
2.Power-off  VM from vcenter

VM sync should update the VMstate in CS properly.VM should be in Power off state

P1

Negative

 

Vmware/KVM/Xen

32

Suspend the VM from vcenter/xencenter/datacenter

1.deploy a VM  from CS
2.suspend a VM from vcenter

VM sync should update the VMstate in CS properly.

P2

Functional

 

Vmware/KVM/Xen

33

make another host as  not suitable  target and put current host in maintenance mode

make another host as  not suitable  target and put current host in maintenance mode

Migration fails andVM sync should update the VMstate in CS properly

 

Functional

 

Vmware/KVM/Xen

34

shutdown current host and check VMs state


Steps:
1. Deploy A VM from CS
2.shutdown the current host

All the HA enabled VMs moved to another Host  ,CS VM status should sync with hypervisor Vm state

P2

Negative

 

Vmware/KVM/Xen

35

reboot the current host and check VMs sate

Steps:
1. Deploy A VM from CS
2 .reboot the current host

state of the VM should be updaded correctly i.e all the VM should be running state

P2

Negative

 

Vmware/KVM/Xen

36

migrate a VM and perform force reconnect on destionation host

Steps:
1. Deploy A VM from CS
2.migrate the vm to anthoer suitable host
3.Perform force reconnect on the host

VM  states should updated properly

P1

Functional

 

Vmware/KVM/Xen

37

Make host unreachble 

Steps:
1. Deploy A VM from CS
2.unplug the Network cable from host

CS VM status should sync with hypervisor Vm state

P2

Negative

 

Vmware/KVM/Xen

38

Deploy a Vm from Vcenter

Steps:
1.deploy a VM from Vcenter

Vmsync should ignore VMS deployed outside CS.(?? Need conformation  for this behavior)

P3

Functional

 

Vmware/KVM/Xen

39

vm stuck in starting state

steps:
1. deploy large Vm
2.simulate the situation where VM stuck in starting state( eg:restart the MS while Vm start operation in progess)

CS vmsync should update the VM state properly .i.e should match with hypervisor's VM state

P2

Functional

 

Vmware/KVM/Xen

40

VM  went to  error state

steps:
1. deploy large Vm
2.simulate the situation where VM state become error  ( eg:Stop the  MS while Vm start operation in progess)

CS vmsync should update the VM state properly .i.e should match with hypervisor's VM state

P2

Functional

 

Vmware/KVM/Xen

41

VM stuck in stopping state

steps:
1. deploy a VM
2.simulate the situation where VM stuck in stopping state( eg:restart the MS while stop operation in progess)

CS vmsync should update the VM state properly .i.e should match with hypervisor's VM state

P3

Functional

 

Vmware/KVM/Xen

 

 

 

 

 

 

 

 

 

DRS

 

 

 

 

 

 

42

deploy all VMs in a specific host on DRS enabled cluster

Setup DRs cluster with 2 hosts  and automation mode as paritial
Steps:
1.Add a host tag
2.create service offering by providing host tag details.
3.deploy all the Vms in secific host(using abve service offering)

DRS will move some of the VMS to another host  and CS should sync and udate the Vm states

P1

Functional/sanity

 

Vmware

43

deploy all VMs in a stopped state  in a specific host on DRS enabled cluster

Setup DRs cluster with 2 hosts  and automation mode as paritial
Steps:
1.Add a host tag
2.create service offering by providing host tag details.
3.deploy all the Vms in secific host(using abve service offering)

 

P2

Functional

 

Vmware

44

deploy all VMs in specific host and migrate all VMS to another host

Setup DRs cluster with 2 hosts  and automation mode as Fully automated
Steps:
1.Add a host tag
2.create service offering by providing host tag details.
3.deploy all the Vms in secific host(using abve service offering)
4. migrate all the vms to anther host

DRS will perform loadbalancingof VMs and CS should update  and show the VM details propelry

P2

Functional

 

Vmware

45

load imbalance triggers migrating VM while VM in starting state

Setup DRs cluster with 2 hosts  and automation mode as Fully automated
Steps:
steps:
1. deploy large Vm
2.Simulate the situation(by increasing the the load on CPU on exiting vms) where load imbalance triggers migrating VM while VM in starting state

CS should sync  the VMs state properly

P2

Functional

 

Vmware

46

load imbalance triggers Vm relocation while VMs  in live migration state

Setup DRs cluster with 3hosts  and automation mode as Fully automated

steps:
1. deploy large Vm on host1
2.migrate VM to  host2
2.Simulate the situation(by increasing the the load on CPU on exiting vms host2) where load imbalance triggers migrating VM while VM in starting state

CS should sync and update the e VMs state properly

P2

Functional

 

Vmware

47

Add new host to unbalanced DRS cluster

Setup DRs cluster with 2hosts  and automation mode as Fully automated

steps:
1.make sure the existing DRS cluster  load is imbalance by creating few Vms on host1(like 3 vms host1 and 2 vms host2)
2.add another new host from cs



DRS migrate Vms to new host to balance the  load   and CS Vm synch should updat the Vms  state and residing host details  properly.

p1

Functioanl

 

Vmware

48

Migration of System VMs on DRS cluster

Setup DRs cluster with 2 hosts  and automation mode as Fully automated
steps: 
  1.Set up cluster in fully automated mode
   2. Migrate system VMs to new host
    3. Host migrated as per DRS recommendations

System VMs should continue to run from new host

P1

Functioanl

 

Vmware

49

Set up anti-affinity rules

Setup DRs cluster with 2 hosts  and automation mode as Fully automated
Steps:  
 1.Set up affinity rule for 2 VMs to be on different hosts
 2.Bring down one of the hosts
  3.The VM in that host should get migrated to the 3rd host

VM is running with the correct host and other details

P1

Functioanl/sanity

 

Vmware

50

migration of vms due to resources (like CPU )crunch

Setup DRs cluster with 2 hosts  and automation mode as Fully automated

Steps:
1.setup up a cluster with DRS in full automated mode

2  create few vms on one host

3. run the load generating scripts or any tools like cpu burn  to increase resource utilization(cpu)

Uservms should move recommended host automatically and same thing should be reflected in CS

P1

Functioanl

 

Vmware

51

Setup the affinity rules

Setup DRs cluster with 2 hosts  and automation mode as Fully automated
 Steps:

 1.  Set up affinity rule for 2 VMs to be on same hosts
  2.Migrate vm1 from one host to another another host

Both VMS should present in sigle host when we move one vm from one host to another host.

P1

Functioanl

 

Vmware

52

Host shutdown

Setup DRs cluster with 2 hosts  and automation mode as Fully automated
Steps:
1.   Set up cluster in fully automated mode
  2.  Bring down on the host(force shutdown?)
  

VMs should move to other host

P2

Functioanl/negative

 

Vmware

53

VM Migration - with migration threshold set to a particular level

Setup DRs cluster with 2 hosts  and automation mode as Fully automated

1.migration threshold set to a particular level

2 Cluster set up in fully automated mode
3. Set migration threshold to something other than default
4.Perform Migrate VM
    Recommendation appears based on host utilization and VM is automatically migrated to the most suitable host
   

VM is migrated to new host,VM  state should be sync.

P2

Functional

 

Vmware

54

deploy a VM in specified host (using host tags)and restrat a VM

Setup DRs cluster with 2 hosts  and automation mode as Fully automated
Steps:
1. Deploy A VM  in specified state
2.restart the VM

VM should be rebooted successfullly and VM  state should be synch

P2

Functional

 

Vmware

55

Check the db schema for newly added fields

Install the Management Server and setup the DB
 Once the installation is successful,open the cloud db  and check the vm_instance  table for newly added columns/constrains:
new cloumns:

power_host
power_state_update_time
power_state_update_count
power_host

Constraint:
fk_vm_instance__power_host

All the newly introduced db columns should present in the vm_instance  tables

P1

Functional

 

Vmware/KVM/Xen

  • No labels