From: Uri Lublin <uril@qumranet.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Dror Russo <dror@qalogic.com>
Subject: Re: [ANNOUNCE] kvm-autotest
Date: Tue, 15 Jul 2008 04:22:23 +0300 [thread overview]
Message-ID: <487BFBCF.7090307@qumranet.com> (raw)
In-Reply-To: <20080712153132.GR4188@us.ibm.com>
Ryan Harper wrote:
> * Uri Lublin <uril@qumranet.com> [2008-07-10 07:42]:
>> Marcelo Tosatti wrote:
>>> On Sun, Jul 06, 2008 at 01:16:13PM +0300, Uri Lublin wrote:
>>>
>>> - As you mention, it should reuse the server/client model for running
>>> tests inside guests. I hacked up a "kvm_autotest" test that
>>> basically does:
>>>
>>> tests = ["linus_stress", "bash_shared_mapping", "rmaptest", "tsc",
>>> "scrashme", "isic", "sleeptest", "libhugetlbfs", "..."]
>>>
>>> vm.ssh.scp_to_remote(autotest_tarball, '/root')
>>> (s,o) = vm.ssh.ssh('tar zvxf kvm-autotest.tar.gz')
>>> for i in range(0, len(tests)):
>>> (s,o) = vm.ssh.ssh('kvm-autotest/client/bin/autotest ' +
>>> 'kvm-autotest/client/tests/' + tests[i] +
>>> '/control')
>>> print(o)
>>>
>>> Which poorly replicates what the client/server infrastructure already
>>> provides. IMO its a waste of time to write specialized client
>>> tests (other than virt specific ones).
>>>
>> You see guests as clients and the host as the server.
>> We were thinking of the host as a client and multi-host operations to be
>> done by a server. guest-operations would be done using ssh (for linux
>> guests) as your example above. You make a good point that we can use
>> server/client infrastructure for guest operations. As it is simpler to
>> write autotest client tests, and we thought most of the tests would be run
>> as client tests, we want to postpone the server tests and focus on adding
>> tests and guests to the matrix.
>
> It's definitely worth looking at the autotest server code/samples.
> There exists code in-tree already to build an deploy kvm via autotest
> server mode which a single machine can drive the building, installing,
> creation of guests on N number of clients, directing each guest
> image to run various autotest client tests, collecting all of the
> results.
>
> See autotest/server/samples/*kvm*
>
> A proper server setup is a little involved[1] but much more streamlined
> these days.
>
Let's think of a guest-installation test. Would you implement it on the server
or on the client ?
What do you plan for non-linux guests ?
We'll try this little exercise of writing a kvm-test on the server side and on
the client side and compare complexity.
Thanks,
Uri.
next prev parent reply other threads:[~2008-07-15 1:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 10:16 [ANNOUNCE] kvm-autotest Uri Lublin
2008-07-09 15:43 ` Marcelo Tosatti
2008-07-10 12:09 ` Uri Lublin
2008-07-12 15:31 ` Ryan Harper
2008-07-15 1:22 ` Uri Lublin [this message]
2008-07-15 7:39 ` Dor Laor
2008-07-15 12:32 ` Ryan Harper
2008-07-16 23:11 ` Uri Lublin
2008-07-17 0:08 ` Ryan Harper
2008-07-21 14:43 ` Uri Lublin
-- strict thread matches above, loose matches on Subject: below --
2008-07-12 14:27 Marcelo Tosatti
2008-07-15 1:02 ` Uri Lublin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=487BFBCF.7090307@qumranet.com \
--to=uril@qumranet.com \
--cc=dror@qalogic.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=ryanh@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox