From: Brian Behlendorf <behlendorf1@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Language choice for Lustre tests
Date: Thu, 25 Oct 2012 10:23:13 -0700 [thread overview]
Message-ID: <1351185793.14408.283.camel@pip> (raw)
In-Reply-To: <BF3E1573-A1E3-47DF-B1B1-866EB65A0D49@xyratex.com>
On Wed, 2012-10-24 at 15:05 -0700, Nathan Rutman wrote:
> On Oct 24, 2012, at 1:02 PM, "Gearing, Chris" <chris.gearing@intel.com> wrote:
>
> > Nathan,
> >
> > I'm not 100% sure what you are proposing here, your LAD presentation suggested a 'tune-up' of the current test framework rather than a complete re-write. Which of the two are we discussing?
> Both...
> >
> The requirements on the framework language are more relaxed, but for ease of development and developer sanity, I assume that the framework language should match the test language. So I'm using the test language as the requirements driver, and to gage community preference for that test language.
Before embarking on building yet another new and custom framework for
Lustre we should evaluate some existing frameworks. For example, the
Autotest project was specifically designed to test the Linux kernel.
It's open source, looks active, is flexible, and there is detailed
documentation on how to write tests. Plus it was designed specifically
for testing the kernel so there are likely existing file system tests.
http://autotest.github.com/
"Autotest is a framework for fully automated testing. It is
designed primarily to test the Linux kernel, though it is useful
for many other functions such as qualifying new hardware. It's an
open-source project under the GPL and is used and developed by a
number of organizations, including Google, IBM, Red Hat, and many
others."
> Based on the responses so far, it seems that there is a fairly clear preference for Python as a test language, and so I'll propose that Python should be used shorter-term to start replacing test-framework.
If we decide the Autotest framework is a good fit then we'll want to
write the tests in python to be consistent with the framework language.
However, for a first cut it looks like you could use the existing bash
tests largely unmodified.
--
Thanks,
Brian
next prev parent reply other threads:[~2012-10-25 17:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 20:02 [Lustre-devel] Language choice for Lustre tests Gearing, Chris
2012-10-24 22:05 ` Nathan Rutman
2012-10-24 22:09 ` Colin Faber
2012-10-25 17:23 ` Brian Behlendorf [this message]
2012-10-25 18:04 ` Nathan Rutman
2012-10-25 21:17 ` Prakash Surya
2012-10-25 21:36 ` Nathan Rutman
2012-10-25 21:50 ` Nathan Rutman
2012-10-25 22:13 ` Prakash Surya
2012-10-25 22:19 ` Roman Grigoryev
2012-10-25 18:20 ` Gearing, Chris
2012-10-25 19:24 ` Nathan Rutman
2012-10-25 21:13 ` Christopher J. Morrone
2012-10-25 21:28 ` Nathan Rutman
2012-10-25 21:52 ` Prakash Surya
2012-10-26 6:24 ` Kilian Cavalotti
2012-10-26 8:52 ` Roman Grigoryev
2012-10-26 11:53 ` Kilian Cavalotti
-- strict thread matches above, loose matches on Subject: below --
2012-10-25 18:38 Gearing, Chris
2012-10-23 18:36 Nathan Rutman
2012-10-23 19:39 ` Jacques-Charles Lafoucriere
2012-10-24 6:31 ` Roman Grigoryev
2012-10-24 7:18 ` Kilian Cavalotti
2012-10-24 8:44 ` Roman Grigoryev
2012-10-24 16:30 ` DEGREMONT Aurelien
2012-10-23 20:05 ` Kilian Cavalotti
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=1351185793.14408.283.camel@pip \
--to=behlendorf1@llnl.gov \
--cc=lustre-devel@lists.lustre.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 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.