On 05/08/2014 06:29 PM, Lucas Meneghel Rodrigues wrote:
Ok, I finally had the time to read your documents. Quite the thought provoking read, in fact :)The base concepts are solid, we really want to optimize test setup/cleanup time, so using the test node transverse algorithm and mechanisms to store states makes a ton of sense. I guess I tried to stay away from qcow2 snapshots because I did not want to rely heavily on part of the very functionality that is being tested (besides good ol' copy is way simpler), but I think it is time to abandon this fear. The biggest concern here is how much of that involved machinery has to be learned by the virt test developer and how much is transparent. See, virt test developers (part of the intended audience) are very smart, but are short in time and energy to grasp fairly complex concepts just to write tests. If all the resolution of variants and steps is transparent and people only have to learn a couple of new keywords, I'd say that is fine.
That's exactly what we do. We simply include two parameters "get_state" and "set_state" to define a starting and ending vm state for a test or a set of tests. The parameters behave just like any normal parameters in the config files - they can be overwritten, separated in variants, etc. All that a test developer should now is which state is needed for his test (which setup he could reuse, the minimal being freshly installed vm) and would he/she like to leave a setup for other tests (include a "set_state" parameter in his test definition).
Anyway, that's one impressive, state of the art work. Kudos to you and your team! As for me, I'm working on a simple implementation for our experimental test framework. If you want to take a look: https://github.com/avocado-framework/avocado/pull/60
I will definitely check it out - a young test framework sounds like the perfect place for similar ideas as the intent can be added from the very beginning.
Thank you for all of your comments! Plamen
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
