Hi folks, after some discussion we had I'd like to update the proposal
of moving the current kvm autotest only libraries to a shared location
inside autotest. Differences from the previous proposal:

* Put the new packages under client directory instead of client/bin.
* Have a kvm package for code that is far too kvm specific

So this is what we envision for the code organization (hope the short,
condensed version is easy enough to understand):

Libraries with very specific kvm code:

from autotest_lib.client.kvm import monitor
from autotest_lib.client.kvm import installer

Libraries shared by several hypervisors testing:

I propose to merge the library that is going to hold the environment
class and the pre/postprocessing code as:

from autotest_lib.client.virt import env

Other libs:

from autotest_lib.client.virt import scheduler
from autotest_lib.client.virt import utils
from autotest_lib.client.virt import test_utils
from autotest_lib.client.virt import vm
from autotest_lib.client.virt import rss_client

Libraries that can be used by all client side tests

from autotest_lib.client.bin import test_config
from autotest_lib.client.bin import subprocess


_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest

Reply via email to