kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: KVM List <kvm@vger.kernel.org>
Subject: Re: [RFC] KVM-Autotest: basic parallel test execution
Date: Sun, 17 May 2009 22:43:46 +0300	[thread overview]
Message-ID: <4A1068F2.9070706@redhat.com> (raw)
In-Reply-To: <1294159996.47211242571742642.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>

Michael Goldish wrote:
> Drawbacks:
> - requires some initial work to be done by the user -- the user has to define exactly where each test should run
>   

For me, this is a major drawback.  I'd really like a fire-and-forget 
solution.  If I have to spend my own time getting this to work, vs. 
waiting longer for the tests to run on their own, I'll just be lazy.

> - test sets need to be modified when tests or hosts are added/removed, to include/exclude them
>   

This is also annoying -- and likely to stop me from updating.

> We'd like to get some feedback on this -- is it usable, comfortable, do you have any suggestions, etc. We'll also be happy to answer questions.
> There are no actual patches attached to this message because the implementation is trivial and we want to focus on the user's point of view.
>
>   


I'd really like this to be automated, just specify a set of machines and 
have the jobs distributed.  Furthermore, it is very important to utilize 
the existing hosts better.  A 4-core 4GB server can easily run a 2x smp 
1GB guest and 2 other uniprocessor 1GB guests.  It's wasteful to add 
more servers when the existing servers are underutilized.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2009-05-17 19:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <360943614.47181242571294363.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-17 14:49 ` [RFC] KVM-Autotest: basic parallel test execution Michael Goldish
2009-05-17 19:43   ` Avi Kivity [this message]
2009-05-20 20:21     ` Mike Burns
2009-06-01  8:02       ` Avi Kivity
2009-05-20 20:52   ` Ryan Harper
2009-05-20 21:12     ` Mike Burns
2009-05-21 11:51       ` Ryan Harper
2009-05-24 14:46     ` Avi Kivity
     [not found] <1176066158.108921242854472990.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-20 21:32 ` Michael Goldish
     [not found] <731194019.115721242860907674.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-20 23:15 ` Michael Goldish
2009-05-21 12:11   ` Ryan Harper

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=4A1068F2.9070706@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mgoldish@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).