autotest/autotest — pull request #508 by chuanchang (2012-08-09 08:27:08+00:00)
Title: Introducing virt-v2v test

This is a patchset introducing virt-v2v test. We've been working during the last 2 months
to provide this pilot test, and get many help from autotest guys during the development,
I would like to thank everyone and especially Yiqiao Pu, Xiaoqing Wei and Amos Kong.

Each patch tries to explain some core concepts behind the work, but pretty much we are using
virt-v2v cmdline tool for automatically converting and importing an existing virtual machines
to libvirt-managed KVM, or an open manageable virtualized environment - oVirt.

For these 2 different input method/target (Libvirt and oVirt), we reuse current libvirt-autotest
as libvirt input target, and implement a new oVirt module as oVirt input target, and using SDK
for the oVirt engine API(as a RESTful API) to manipulate resources in oVirt such as Data Centers,
Clusters, Hosts, Storage Domains, VMs, etc.

At present, we haven't cover everything into our oVirt module, it only includes some necessary
API implementation for virt-v2v requirement. However, it's very easy to extend new functions to
support oVirt autotest in the future.

For v1 patchset, we got many positive feedback and good advise from autotest upstream, and we made a great improvement for v2 patchset, also got some feedback from upstream, for example, anything out of client or shared modules are out of limits for code that is supposed to run on a client, in addition, I found a parameter match issue on v2 patchset, so v3 is expected.

For v3 patchset, we done some small changes such as sharing SSH creation method for both server and client end, and fixed a parameter match issue in the constructor function of the class LinuxVMCheck.
Please review our v3 patchset and raise your feedback and good advise again.

Thanks in advance,
Alex Jia
Wayne Sun