GitHub user abhinavroy02 opened a pull request:
https://github.com/apache/cloudstack/pull/139
CLOUDSTACK-8357 Add Test cases for vMotion support on VMFS as primary st...
This commit has the vMotion related test cases. Following are the tests
1. Create a VM and migrate it.
2. Migrate only ROOT volume of VM and check for vmx and vmdk files in
storage.
3. Migrate VM and its ROOT volume and check for vmx and vmdk files in
storage.
4. Attach Data disk to VM and then migrate VM and all its volumes followed
by the check for files.
5. Upload a volume, attach it to VM and then migrate VM and all its volumes
followed by the check for files.
6. Take Volume snapshots of all the volumes then migrate VM and all its
volumes followed by the check for files.
7. Resize the Data disk then migrate VM and all its volumes followed by the
check for files.
8. Restore the VM then migrate VM and all its volumes followed by the check
for files.
All these are part of a test path so there is a single test written which
has all the cases.
Here is the output after executing them locally:
Migrate VMs/Volumes on VMware with VMFS storage ... === TestName:
test_01_migrate_root_and_data_disk_live | Status : SUCCESS ===
ok
----------------------------------------------------------------------
Ran 1 test in 855.918s
OK
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/abhinavroy02/cloudstack CS-8357
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/139.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #139
----
commit dedc860a62bbfc12971b3661fc654f3b8687c1ca
Author: Abhinav Roy <[email protected]>
Date: 2015-04-01T17:48:40Z
CLOUDSTACK-8357 Add Test cases for vMotion support on VMFS as primary
storage
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
