All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Micah Parrish" <micah.parrish@hpe.com>
To: kernelci@groups.io
Subject: Re: [kernelci] getting started?
Date: Thu, 28 Jun 2018 11:53:35 -0600	[thread overview]
Message-ID: <4f4fcc85-f40e-08d7-07da-bc0ed619efcb@hpe.com> (raw)
In-Reply-To: <CAH+k93Hn6wDEPU6qMsRfSFS0_ApdzxR6kGumnho9iDNWqvxfFg@mail.gmail.com>

I'm trying to redeploy a mix of prototypes and production systems as a 
very low touch "top of tree kernel test" farm.  This give us early 
warning when an kernel change has affected our HW or FW.  Kernelci.org 
does almost exactly what I'd like to do, but I need to keep an instance 
in-house because of prototype confidentiality requirements.  If that 
works out I'm open to putting some production servers in the main pool 
somehow.

Is there a diagram of how all the parts fit together?

-Micah


On 06/28/2018 07:11 AM, Matt Hart wrote:
> Hi Micah
>
> There are indeed a lot of moving parts. You could run your own web UI 
> and API fairly easily but there's no guides to setup the build system 
> and the boot testing (LAVA) lab.
> What are you trying to achieve? Could it be with KernelCI rather than 
> your own setup?
>
> Matt
>
> On 22 June 2018 at 19:35, Micah Parrish <micah.parrish@hpe.com 
> <mailto:micah.parrish@hpe.com>> wrote:
>
>     I really like what you've done with kernelci.org
>     <http://kernelci.org>, and I'm interested in running it in a
>     semi-isolated x86 test lab.  Do you have a recipe I can follow for
>     doing this?  It seems like there are a lot of moving parts, but I
>     don't quite see how they all fit together yet.
>
>     Regards,
>
>     Micah Parrish
>     Linux OS Engineer
>     Hewlett-Packard Enterprise
>
>
>
>
> 



  reply	other threads:[~2018-06-28 17:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 12:34 Testing with distros Guillaume Tucker
2018-06-22 18:35 ` getting started? micah.parrish
2018-06-28 13:11   ` [kernelci] " Matt Hart
2018-06-28 17:53     ` Micah Parrish [this message]
2018-07-26 22:22       ` Kevin Hilman
2018-06-27 23:05 ` [kernelci] Testing with distros Kevin Hilman
2018-06-28 13:13   ` Matt Hart
2018-07-02  8:07   ` Tomeu Vizoso

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=4f4fcc85-f40e-08d7-07da-bc0ed619efcb@hpe.com \
    --to=micah.parrish@hpe.com \
    --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 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.