DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.

DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
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(kvm) | Hypervisor |
1 | Stop a VM from vcenter/xencenter/datacenter | Steps: | Vm should be stopped successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
2 | Stop CS HA enabled VM | Steps: | Vm should be stopped successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
3 | Stop a VM from CS | Steps: | Vm should be stopped successfully and VM sync should update the VMstate in CS properly | P2 | Functional | Pass | Vmware/KVM/Xen |
4 | Stop &start VM from CS | Steps: | Vm should be stopped&started successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Pass | Vmware/KVM/Xen |
5 | stop &start VM from vcenter/xencenter/datacenter | Steps: | Vm should be stopped &started successfully and VM sync should update the VMstate in CS properly | P1 | Functional/Sanity | Pass | Vmware/KVM/Xen |
6 | Stop a Vm from CS and start a VM from vcenter/xencenter/datacenter | Steps: | Vm should be stopped &started successfully and CS VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
7 | Stop the system VMs from vcenter/xencenter/datacenter | 1.Make sure system Vm and running in the setup. | System vms will be stopped successfully and will start again by the CS and system Vms will | P2 | Functional | Fail | Vmware/KVM/Xen |
8 | Stop and start system VM from vcenter | 1.Make sure system Vm and running in the setup. | System vms will be stopped and started successfully | P1 | Functional | Pass | Vmware/KVM/Xen |
9 | Stop and start router VM from vcenter/xencenter/datacenter | 1.Make sure router Vm running in the setup. | router vms will be stopped and stared successfully. | P1 | Functional | Pass | Vmware/KVM/Xen |
10 | stop& start a VM when current host resources are full | 1. Deploy A VM from CS | 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. | 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. | 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: | Vm should be rebooted successfully and VM sync should update the VMstate in CS properly | P2 | Functional | Pass | Vmware/KVM/Xen |
14 | reboot VM from vcenter | Steps: | Vm should be rebooted successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Pass | Vmware/KVM/Xen |
15 | migrate a VM and stop VM | Steps: | migrated VM should stop successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
16 | migrate a VM and stop &start VM | Steps: | migrated VM should stop &start successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
17 | migrate a VM and reboot VM | Steps: | migrated VM should reboot successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
18 | migrate a VM and reset a VM | Steps: | migrated VM should reset successfully and VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
19 | migrate a VM and destroy and restore | Steps: | VM should be in stopped state | P2 | Functional | Fail | Vmware/KVM/Xen |
20 | migrate a VM and stop a VM CS &start a VM from vcneter/vmmanager/xencenter | Steps: | VM should be in start state | P1 | Functional | Fail | Vmware/KVM/Xen |
21 | migrate a VM and reboot VM from vcneter | Steps: | migrated VM should reboot successfully and VM sync should update the VMstate in CS properly | P1 | Functional/sanity | Fail | Vmware/KVM/Xen |
22 | deploy a VM in stopped state and start a VM | Steps: | 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: | Vm should be in stop state only | P2 | Functional |
| Vmware/KVM/Xen |
24 | make cluster as unmnaged to manage | Steps: | 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: | VM sync should update the VMstate in CS properly,CS VM status should sync with hypervisor Vm state | P1 | Functional/sanity | Fail | Vmware/KVM/Xen |
26 | migrate few vms from vcneter and make cluster as managed | Steps: | VM sync should update the VMstate in CS properly | P1 | Functional | Fail | Vmware/KVM/Xen |
27 | deploy Vms and put host in maintenance | Steps: | all the VMs(nonHA) in stopped state | P1 | Functioanl | Fail | Vmware/KVM/Xen |
29 | deploy HA enabled VMs and put host in maintenance | Steps: | All the HA enabled VMs moved to another Host ,CS VM status should sync with hypervisor Vm state | P1 | Functional | Fail | Vmware/KVM/Xen |
30 | Shutdown VM form console | 1.deploy a VM | VM sync should update the VMstate in CS properly and VM shoud be shutdown state | P2 | Functional | Fail | Vmware/KVM/Xen |
31 | Poweroff VM from vcenter/xencenter/datacenter | 1.deploy a VM from CS | VM sync should update the VMstate in CS properly.VM should be in Power off state | P1 | Negative | Fail | Vmware/KVM/Xen |
32 | Suspend the VM from vcenter/xencenter/datacenter | 1.deploy a VM from CS | VM sync should update the VMstate in CS properly. | P2 | Functional | Fail | 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 |
| All the HA enabled VMs moved to another Host ,CS VM status should sync with hypervisor Vm state | P2 | Negative | Fail | Vmware/KVM/Xen |
35 | reboot the current host and check VMs sate | Steps: | state of the VM should be updaded correctly i.e all the VM should be running state | P2 | Negative | Fail | Vmware/KVM/Xen |
36 | migrate a VM and perform force reconnect on destionation host | Steps: | VM states should updated properly | P1 | Functional |
| Vmware/KVM/Xen |
37 | Make host unreachble | Steps: | CS VM status should sync with hypervisor Vm state | P2 | Negative |
| Vmware/KVM/Xen |
38 | Deploy a Vm from Vcenter | Steps: | Vmsync should ignore VMS deployed outside CS.(?? Need conformation for this behavior) | P3 | Functional |
| Vmware/KVM/Xen |
39 | vm stuck in starting state | steps: | 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: | 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: | 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 | 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 |
| 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | All the newly introduced db columns should present in the vm_instance tables | P1 | Functional |
| Vmware/KVM/Xen |