Re: [kernelci] getting started?

["Kevin Hilman" <khilman@baylibre.com>]

"Micah Parrish" <micah.parrish@hpe.com> writes:

> 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?

The long delay in responding meant that no, there was no diagram.  Our
docs are pretty minimal, but we've begun an attempt to improve that
on the wiki for the kernelci-doc project: https://github.com/kernelci/kernelci-doc/wiki

The sub-page for setting up a local instance[1] would be a good start,
and to compliment that, I just whipped up this draw.io diagram[1] that
tries to show graphically how all the kernelCI pieces fit together in a
full CI loop. Most items have links to the various github projects where
the code lives.

I admit that it's very primitive, but it should at least help you get
started seeing how all the parts fit together.

Hope that helps,

Kevin

[1] https://github.com/kernelci/kernelci-doc/wiki/Setting-up-a-local-development-instance
[2] https://drive.google.com/file/d/1x2SXt24ZNzuk3SfBzsQpw_RnLOcF3vWd/view?usp=sharing


> -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
>>
>>
>>
>>
>>
>
>
>
>