From: jason wang <jasowang@redhat.com>
To: sudhir kumar <smalikphy@gmail.com>
Cc: kvm@vger.kernel.org, uril@redhat.com, mrodrigu@redhat.com
Subject: Re: kvm-autotest: The automation plans?
Date: Thu, 14 May 2009 14:52:13 +0800 [thread overview]
Message-ID: <4A0BBF9D.8050009@redhat.com> (raw)
In-Reply-To: <a50cf5ab0905131051o40847d2bl7c5497f7a5abde61@mail.gmail.com>
sudhir kumar 写道:
> Hi Uri/Lucas,
>
> Do you have any plans for enhancing kvm-autotest?
> I was looking mainly on the following 2 aspects:
>
> (1).
> we have standalone migration only. Is there any plans of enhancing
> kvm-autotest so that we can trigger migration while a workload is
> running?
> Something like this:
> Start a workload(may be n instances of it).
> let the test execute for some time.
> Trigger migration.
> Log into the target.
> Check if the migration is succesful
> Check if the test results are consistent.
>
We have some patches of ping pong migration and workload adding. The
migration is based on public bridge and workload adding is based on
running benchmark in the background of guest.
> (2).
> How can we run N parallel instances of a test? Will the current
> configuration be easily able to support it?
>
> Please provide your thoughts on the above features.
>
>
The parallelized instances could be easily achieved through
job.parallel() of autotest framework, and that is what we have used in
our tests. We have make some helper routines such as get_free_port to be
reentrant through file lock.
We've implemented following test cases: timedrift(already sent here),
savevm/loadvm, suspend/resume, jumboframe, migration between two
machines and others. We will sent it here for review in the following weeks.
There are some other things could be improved:
1) Current kvm_test.cfg.sample/kvm_test.cfg is transparent to autotest
server UI. This would make it hard to configure the tests in the server
side. During our test, we have merged it into control and make it could
be configured by "editing control file" function of autotest server side
web UI.
2) Public bridge support: I've sent a patch(TAP network support in
kvm-autotest), this patch needs external DHCP server and requires nmap
support. I don't know whether the method of original kvm_runtes_old(DHCP
server of private bridge) is preferable.
next prev parent reply other threads:[~2009-05-14 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 17:51 kvm-autotest: The automation plans? sudhir kumar
2009-05-13 18:00 ` Michael Goldish
2009-05-14 10:22 ` sudhir kumar
2009-05-13 18:38 ` Lucas Meneghel Rodrigues
2009-05-14 6:52 ` jason wang [this message]
2009-05-14 10:29 ` sudhir kumar
2009-05-14 10:50 ` Michael Goldish
2009-05-15 8:40 ` jason wang
2009-05-19 11:24 ` sudhir kumar
2009-05-20 9:29 ` jason wang
2009-05-20 12:14 ` Uri Lublin
[not found] <819364962.208261242291936661.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-14 9:10 ` Michael Goldish
2009-05-15 3:38 ` jason wang
[not found] <197705536.212021242299098670.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-14 11:13 ` Michael Goldish
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=4A0BBF9D.8050009@redhat.com \
--to=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mrodrigu@redhat.com \
--cc=smalikphy@gmail.com \
--cc=uril@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.