Re: [RFC][KVM-AUTOTEST] Work to get autotest kvm merged back upstream

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Lucas Meneghel Rodrigues !

I'm Alexey from Red Hat Israel, and I do QA on both KVM and KVM Autotest.

>  4 We want to make it easy for people to add new tests to the framework.
> We are unsure if the current way we define the tests (all of them under
> the file kvm_tests.py) is good maintainability-wise. Unfortunately I am
> new to KVM and I still don't have a clear idea if we could use a
> different approach.
>
There is a good idea sent to us by someone, that we should make some
of our tests dynamically loadable.

It will look like:
cliest/tests/kvm_runtest_2/tests

"Tests" and "Tests again" is useful, because first tests will have
tests that are dependent on autotest generic framework, and second
tests will be useful for tests that dependent on KVM Autotest
framework.
Basically it was proposed that all "Tests again" will have a structure
like "test_testname.py", and kvm_runtest2.py will load those modules
dynamically according to filename.
And automatically run function "run_testname()".

This makes it very easy to external contributors to contribute,
without breaking someone else's code.

> For 3 and 4, we will still need more time to work on this. However, they
> are not crucial to get all the stuff merged back with upstream.
>
>  5 Though there are plans of moving from subversion to git, we still
> don't know when that will happen. So it might take a little time.
>
> I think 5 doesn't hold us back from merging back with upstream as soon
> as possible. I talked with some folks at google and they agree that we
> should merge soon.
>

Git is not a problem, because KVM Autotest is internally developed
using Git at Red Hat.

> So the current plan is:
>
>  * Finish the patches to make the code base comply with upstream
> standards, give it good testing.
>  * Finish replacing kvm_log with the logging module and test everything
>  * Send a patch upstream adding the kvm test module
>  * From there, development would happen using cross posting between the
> autotest mailing list and the KVM one.
>
> I hope this all makes sense. Comments?
>
> Best regards,
>
> --
> Lucas Meneghel Rodrigues
> Software Engineer (Virtualization)
> Red Hat - Emerging Technologies
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
-Alexey Eromenko "Technologov"
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux