Hi folks, I am here planning our activities for the next year, and our big task for the 1st quarter of the year is the KVM autotest refactor, to accomodate other hypervisor's testing.
Eduardo sent a patchset creating a KVM package inside the kvm test directory. After some discussion with Michael, we think it is better to create the package, but on its more long-term location, autotest_lib.client.bin. So, my proposition is: Libraries that can be used by all client side tests KVM configuration: The kvm config class can be moved to autotest_lib.client.bin.test_config, with a new class name ConfigCartesian. from autotest_lib.client.bin import test_config KVM subprocess: That can be moved to a new autotest_lib.client.bin.subprocess module. I would like to move all autotest APIs to control subprocess in there, such as the current utils.run, utils.system and friends. from autotest_lib.client.bin import subprocess Libraries that can be used by virtualization testing in general We can create a package autotest_lib.client.bin.virt, with the following libraries: KVM monitor: from autotest_lib.client.bin.virt import monitor KVM environment class: from autotest_lib.client.bin.virt import env KVM postprocessing module: from autotest_lib.client.bin.virt import env_processing KVM scheduler: from autotest_lib.client.bin.virt import scheduler KVM utils: from autotest_lib.client.bin.virt import utils KVM test utils: from autotest_lib.client.bin.virt import test_utils KVM vm class: from autotest_lib.client.bin.virt import vm KVM rss file transfer: from autotest_lib.client.bin.virt import rss_client I am a bit reluctant to write patches before I have some level of feedback on it, so please let me know what you think. Cheers, Lucas _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
