Test case Id |
Test case description |
Steps |
Expected Result |
Priority |
Xen 6.0.2 |
KVM |
Comments
|
1 |
Storage migration within same cluster |
MigrateVirtualMachine() with VMId , SPId (from the same cluster as the Vm), when VM is in stopped state |
Storage Migration should succeed.
Starting the VM should result in the VM using the new storage pool
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the file system. |
P1 |
Pass |
Pass |
|
2 |
Storage migration within same cluster with 1 data disk |
MigrateVirtualMachine() with VMId with 1 data disk attached to it , SPId (from the same cluster as the Vm), when VM is in stopped state |
Storage Migration should succeed for root volume
Data volume will not be migrated if on the same cluster
Starting the VM should result in the VM using the new storage pool.
Make sure that a new vhd file for this VM is created in the new primary storage pool
The vhd file for this VM should not be present in the Primary storage it originally belonged to
Log in to the Vm . Make sure that you are able to read/write in the root volumes.
Make sure that you are able to read/write in the attached data disks.
|
P1 |
Pass |
Pass |
|
3 |
Storage migration within same cluster with multiple data disks |
MigrateVirtualMachine() with VMId with multiple data disks attached to it , SPId (from the same cluster as the Vm), when VM is in stopped state |
Storage Migration should succeed for root volume and data disk volumes
Starting the VM should result in the VM using the new storage pool
Make sure that a new vhd file for this VM is created in the new primary storage pool
The vhd file for this VM should not be present in the Primary storage it originally belonged to
Log in to the Vm . Make sure that you are able to read/write in the root volumes
Make sure that you are able to read/write to all the attached data disks |
P2 |
Pass |
|
|
4 |
Migration across different clusters |
MigrateVirtualMachine() with VMId , SPId (from a cluster other than the one Vm is currently running), when VM is in stopped state |
Storage Migration should succeed
Starting the VM should result in the VM using the new storage pool
VM should now run in the host that is associated with the cluster where the new storage pool resides.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the file system.
|
P1 |
Pass
|
Pass |
|
5 |
Migration across different clusters |
MigrateVirtualMachine() with VMId with multiple data disks attached to it , SPId (from a cluster other than the one Vm is currently running), when VM is in stopped state |
Storage Migration should succeed for root volume and data disk volumes.
Starting the VM should result in the VM using the new storage pool.
VM should now run in the host that is associated with the cluster where the new storage pool resides.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the root volumes.
Make sure that you are able to read/write to all the attached data disks.
|
P2 |
Pass |
Pass |
|
6 |
Migration with Snapshot |
Take Snapshot - S1 of the root volume and D1 -data disk volume.
MigrateVm to a storage pool in a different cluster.
Take Snapshot - S2 of the root volume and D2 - data disk volume. |
Create a template and start a VM using snapshot S1 . Make sure that the file system of the VM matches the Snapshot S1.
Attach a disk volume created from D1. Make sure the contents of this volume matches
snapshot D1.
Create a template and start a VM using snapshot S2 . Make sure that the file system of the VM matches the Snapshot S1.
Attach a disk volume created from D1. Make sure the contents of this volume matches snapshot D2. |
P1 |
Pass |
|
|
7 |
Migration with ISO attached |
Attach an ISO to a Vm.
MigrateVm to different storage pool. |
After migration make sure that the ISO is still attached to the vm and is accessible. |
P2 |
Pass |
|
|
8 |
Migration across different PODS |
MigrateVirtualMachine() with VMId , SPId (from a pod other than theo one Vm is currently running), when VM is in stopped state |
Storage Migration should succeed.
Starting the VM should result in the VM using the new storage pool.
VM should now run in the host that is associated with the cluster where the new storage pool resides.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the file system. |
P1 |
Pass |
Pass |
|
9 |
Migration across different PODS |
MigrateVirtualMachine() with VMId with 1 data disk attached to it , SPId (from a pod other than the one Vm is currently running), when VM is in stopped state |
Storage Migration should succeed for root volume and data disk volumes.
Starting the VM should result in the VM using the new storage pool.
VM should now run in the host that is associated with the cluster where the new storage pool resides.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the root volumes.
Make sure that you are able to read/write in the attached data disks.
|
P1 |
Pass |
Pass |
|
10 |
Migration with in cluster from one local storage to another |
MigrateVirtualMachine() with VMId , SPId (from the same cluster as the Vm), when VM is in stopped state |
Storage Migration should succeed.
Starting the VM should result in the VM using the new storage pool.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the file system.
|
P2 |
Passed for root vol. For data vol, gives proper error msg |
|
|
11 |
Migration across Pods with local storage |
MigrateVirtualMachine() with VMId with 1 data disk attached to it , SPId (from a pod other than the one Vm is currently running), when VM is in stopped state |
Storage Migration should succeed for root volume and data disk volumes.
Starting the VM should result in the VM using the new storage pool.
VM should now run in the host that is associated with the cluster where the new storage pool resides.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the root volumes.
Make sure that you are able to read/write in the attached data disks. |
P2 |
Pass |
Pass |
|
12 |
Migration across cluster from NFS to local storage |
MigrateVirtualMachine() with VMId with multiple data disks attached to it , SPId (from a cluster other than the one Vm is currently running), when VM is in stopped state |
Storage Migration should succeed for root volume and data disk volumes.
Starting the VM should result in the VM using the new storage pool.
VM should now run in the host that is associated with the cluster where the new storage pool resides.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the root volumes.
Make sure that you are able to read/write to all the attached data disks. |
P2 |
Passed for root vol. For data vol, gives proper error msg |
|
|
13 |
Migration across cluster from local storage to NFS |
MigrateVirtualMachine() with VMId with multiple data disks attached to it , SPId (from a cluster other than the one Vm is currently running), when VM is in stopped state |
Storage Migration should succeed for root volume and data disk volumes.
Starting the VM should result in the VM using the new storage pool.
VM should now run in the host that is associated with the cluster where the new storage pool resides.
Make sure that a new vhd file for this VM is created in the new primary storage pool .
The vhd file for this VM should not be present in the Primary storage it originally belonged to.
Log in to the Vm . Make sure that you are able to read/write in the root volumes.
Make sure that you are able to read/write to all the attached data disks.
|
P2 |
Passed for root vol. For data vol, gives proper error msg |
Passed for root vol. For data vol, gives proper error msg |
|
14 |
Restart MS during Migration |
Use MigrateVirtualMachine() for a Vm.
When the Volume migration is still in progress ,restart the management server. |
Async job should report a failure.
Vm migration should fail. There should be a roll back done. Vm state should get back to" Stopped" and volumes should get back to "Ready" state.
Attempt to start the VM should succeed using the existing (older) storage. |
P2 |
Pass |
|
|
15 |
Migrate volume when VM is running |
Use MigrateVirtualMachine() with VMId , SPId , when VM is in Running state |
Should throw appropriate error. Storage migration can happen only if the Vm is in Stopped state. |
P2 |
Pass |
Pass |
|
