All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: yogi <anantyog@linux.vnet.ibm.com>,
	autotest@test.kernel.org, kvm@vger.kernel.org,
	Ryan Harper <ryanh@us.ibm.com>,
	Michael Goldish <mgoldish@redhat.com>
Subject: Re: [Autotest] [KVM-AUTOTEST PATCH 0/5] KVM test: Support for Parallel install of guest OS
Date: Wed, 10 Feb 2010 11:54:50 -0600	[thread overview]
Message-ID: <20100210175450.GU6083@us.ibm.com> (raw)
In-Reply-To: <1265821989.2273.15.camel@localhost.localdomain>

* Lucas Meneghel Rodrigues <lmr@redhat.com> [2010-02-10 11:14]:
> On Wed, 2010-02-10 at 21:53 +0530, yogi wrote:
> > Hello everyone,
> > 
> > I like to submit a set of patches to enable installing multiple guests
> > in parallel.
> 
> Hi Yogi, great to receive your patches!
> 
> > To install multiple guests in parallel the role of the host and the
> > guest need to be changed. In this patch host acts as a client and the
> > guest acts as server, enabling us to install multiple guest at same
> > time. 
> 
> I see your point, but I am concerned that we already have a parallel
> test execution implementation (see control.parallel), so either your
> patchset needs to fit in with the control.parallel approach or we might
> think of another approach. I have thought of some ideas, will check your
> approach and comment about it soon.

If I've read the patches right,  I believe Yogi is relying upon
control.parallel; these changes are needed to ensure that the
unattended_install test invoked in parallel doesn't clobber itself.
Yogi hit all of the major issues:

1) tftp code uses the same path and filename for each guest; Yogi
switched that to include a per-guest path so we can have multipl
kernel/initrd pairs in flight at the same time

2) only one service side listening server and no way agreeing upon a
port number; Yogi moved the listen to the guest, and now the host pokes
at the pre-defined port in each guest to see if it has completed.



-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  reply	other threads:[~2010-02-10 17:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 16:23 [Autotest] [KVM-AUTOTEST PATCH 0/5] KVM test: Support for Parallel install of guest OS yogi
2010-02-10 16:28 ` [KVM-AUTOTEST PATCH 1/5] " yogi
2010-02-10 16:29 ` [KVM-AUTOTEST PATCH 2/5] " yogi
2010-02-10 16:29 ` [KVM-AUTOTEST PATCH 3/5] " yogi
2010-02-10 17:09   ` Ryan Harper
2010-02-10 17:22   ` [Autotest] " Lucas Meneghel Rodrigues
2010-02-10 17:45     ` yogi
2010-02-10 16:30 ` [Autotest] [KVM-AUTOTEST PATCH 4/5] " yogi
2010-02-10 16:30 ` [KVM-AUTOTEST PATCH 5/5] " yogi
2010-02-10 17:13 ` [Autotest] [KVM-AUTOTEST PATCH 0/5] " Lucas Meneghel Rodrigues
2010-02-10 17:54   ` Ryan Harper [this message]
2010-02-10 19:41     ` Lucas Meneghel Rodrigues
2010-02-10 18:00   ` [Autotest] " yogi

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=20100210175450.GU6083@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=anantyog@linux.vnet.ibm.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    --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 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.