From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel@lists.xen.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: [OSSTEST PATCH [RFC] 0/3] Series short description
Date: Thu, 5 Dec 2013 15:09:41 +0000 [thread overview]
Message-ID: <20131205150935.20194.10427.stgit@drall.uk.xensource.com> (raw)
OSSTest: allow for handling multiple guests at the same time
via the ts-debian-install, ts-debian-fixup and
ts-guest-{start,stop,destroy} test scripts.
The idea is to enable something like that:
$ OSSTEST_JOB=test-amd64-amd64-xl
$ export OSSTEST_JOB
$ ./ts-debian-install host=tg03 debian1 debian2 debian3
$ ./ts-debian-fixup host=tg03 debian1 debian2 debian3
$ ./ts-guest-start host=tg03 debian1 debian2 debian3
$ ./ts-guest-stop host=tg03 debian1 debian2
$ ./ts-guest-destroy host=tg03 debian3
In fact, when wanting to use OSSTest for some fairly complex test
or benchamrk that involves more than one or two VMs, I think
it could be convinient to install, start, stop, etc., them like
this, rather than having to call each script for all the domains.
It should also save some time, when it comes, for example, to
starting domains, as the operation is first requsted for all of
them, and only after that we start checking wether they're up
(the idea being that when we start checking, after having started
the last one, the first one have probably finished booting).
It's going to be mostly useful in standalone mode, but
I guess it could allow to write more compact recipes too.
I tested this both as reported above and by issueing a full
`./sg-run-job test-amd64-amd64-xl'.
I can go ahead and do the same for other ts-* scripts but:
1) I don't think is that much relevant/useful to do something
like this in, for instance, ts-guest-migrate or
ts-guest-saverestore
2) given my limited perl skills, I though I better ask for
some early feedback. :-)
Any comments are welcome.
Regards,
Dario
---
Dario Faggioli (3):
ts-debian-install: support for installing multiple guests
ts-debian-fixup: support multiple guests
ts-guest-start, -stop, -destroy: support multiple guests
ts-debian-fixup | 30 ++++++++++++++++++---------
ts-debian-install | 59 +++++++++++++++++++++++++++++++----------------------
ts-guest-destroy | 28 +++++++++++++++++++------
ts-guest-start | 35 ++++++++++++++++++++++---------
ts-guest-stop | 30 ++++++++++++++++++++-------
5 files changed, 123 insertions(+), 59 deletions(-)
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
next reply other threads:[~2013-12-05 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 15:09 Dario Faggioli [this message]
2013-12-05 15:09 ` [OSSTEST PATCH [RFC] 1/3] ts-debian-install: support for installing multiple guests Dario Faggioli
2013-12-05 15:10 ` [OSSTEST PATCH [RFC] 2/3] ts-debian-fixup: support " Dario Faggioli
2013-12-05 15:10 ` [OSSTEST PATCH [RFC] 3/3] ts-guest-start, -stop, -destroy: " Dario Faggioli
2013-12-05 15:25 ` [OSSTEST PATCH [RFC] 0/3] Series short description Ian Jackson
2013-12-05 16:17 ` Dario Faggioli
2013-12-05 17:34 ` Ian Jackson
2013-12-06 9:23 ` Dario Faggioli
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=20131205150935.20194.10427.stgit@drall.uk.xensource.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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).