From: "Bjorn Andersson" <bjorn.andersson@linaro.org>
To: kernelci@groups.io, chuck.lever@oracle.com
Cc: "info@kernelci.org" <info@kernelci.org>,
Bruce Fields <bfields@redhat.com>
Subject: Re: Using kernelci.org for testing Linux NFSD
Date: Tue, 5 Oct 2021 09:57:11 -0700 [thread overview]
Message-ID: <YVyD59X4yXPh2KzX@ripper> (raw)
In-Reply-To: <13C9FF88-C1F6-4127-AAA1-E38A1D59AB96@oracle.com>
On Fri 01 Oct 12:01 PDT 2021, Chuck Lever III wrote:
> Hi-
>
Hi Chuck,
> As co-maintainers of NFSD, we're interested in bringing up a
> CI platform for automating a lot of the tests we do before
> requesting a pull into the Linux kernel. The kernelci.org
> platform caught my eye last week during the talk at LPC.
>
> We have some questions about what can be supported on
> kernelci.org. For example, the tests we need to run involve
> at least two hosts (an NFS client and an NFS server). How
> easy is it to set up that kind of test?
>
> If we want to test features that involve Kerberos, is there
> a KDC available, or would we need to provide a KDC image
> that can be used for our tests?
>
> Thanks for any guidance!
>
In my view, kernelci.org provides two things:
1) A platform that provide build artifacts (i.e kernel images) of
various trees and collects test results from labs booting these builds,
running tests and reporting back results.
2) A set of labs, with pretty much standardized way of running these
tests on artifacts coming from the builder and reporting the results
back.
Given that your testing setup and test cases do differ quite a bit from
what's today seem to happen in the existing labs ("boot a kernel on one
board, run common tests, gather results") my suggestion is that you
automate the process done by these labs on your end and use the common
infrastructure.
I.e. build something that takes a kernel image, boots this on your
machines and runs your test and generate test results in a structured
form.
Then you can plug this in with kernelci (#1 above) using the available
REST API, to get the kernel images and to report the results.
This is what I do for the Qualcomm boards in my lab, where I'm not able
to run the standard lab setup (not sure if that even was a thing when I
started) and it allows me to run more board specific tests - with all
the results reported back to a single place.
Regards,
Bjorn
prev parent reply other threads:[~2021-10-05 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 19:01 Using kernelci.org for testing Linux NFSD Chuck Lever III
2021-10-05 13:07 ` Gustavo Padovan
2021-10-05 13:47 ` Bruce Fields
2021-10-05 14:33 ` Chuck Lever III
2021-10-26 16:51 ` Chuck Lever III
2021-10-05 16:57 ` Bjorn Andersson [this message]
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=YVyD59X4yXPh2KzX@ripper \
--to=bjorn.andersson@linaro.org \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=info@kernelci.org \
--cc=kernelci@groups.io \
/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).