* Contribution as a build and boot tester.
@ 2020-03-17 22:42 Javier Romero
2020-03-23 22:31 ` Kevin Hilman
0 siblings, 1 reply; 3+ messages in thread
From: Javier Romero @ 2020-03-17 22:42 UTC (permalink / raw)
To: info
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
Hi,
My name is Javier, have been working as a Linux sysadmin for the last 10
years and now I'm working as a cloud engineer.
Would like to start contributing as a build and boot tester. I've a
Raspberry PI 3 with ARM Hardware, and a computer with an Intel Core 2 duo.
Thanks for your attention and sorry for the inconvenience.
Best Regards,
[-- Attachment #2: Type: text/html, Size: 633 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Contribution as a build and boot tester.
2020-03-17 22:42 Contribution as a build and boot tester Javier Romero
@ 2020-03-23 22:31 ` Kevin Hilman
2020-03-23 22:41 ` Javier Romero
0 siblings, 1 reply; 3+ messages in thread
From: Kevin Hilman @ 2020-03-23 22:31 UTC (permalink / raw)
To: kernelci, xavinux, info
Hi Javier,
Javier Romero <xavinux@gmail.com> writes:
> My name is Javier, have been working as a Linux sysadmin for the last 10
> years and now I'm working as a cloud engineer.
Thanks for your interest in KernelCI.
> Would like to start contributing as a build and boot tester. I've a
> Raspberry PI 3 with ARM Hardware, and a computer with an Intel Core 2 duo.
Currently, a single Core2 duo won't be very useful to us as an extra
builder, and we already have rpi3 boards in a few of our existing labs.
However, if you'd like to setup your rpi3 into a LAVA lab to better
understand how KernelCI lab works, and potentially add more hardware, I
suggest following our docs for setting up your own LAVA[1]. That doc
doesn't (yet) mention it, but you we now have a dockerized version of a
LAVA lab that hopefully simplifies the learning curve of setting up
LAVA: https://github.com/kernelci/lava-docker/
Kevin
[1] https://github.com/kernelci/kernelci-doc/wiki/Setting-up-a-local-development-instance
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Contribution as a build and boot tester.
2020-03-23 22:31 ` Kevin Hilman
@ 2020-03-23 22:41 ` Javier Romero
0 siblings, 0 replies; 3+ messages in thread
From: Javier Romero @ 2020-03-23 22:41 UTC (permalink / raw)
To: Kevin Hilman; +Cc: kernelci, info
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Thanks, I'll check them out.
El lun., 23 mar. 2020 19:31, Kevin Hilman <khilman@baylibre.com> escribió:
> Hi Javier,
>
> Javier Romero <xavinux@gmail.com> writes:
>
> > My name is Javier, have been working as a Linux sysadmin for the last 10
> > years and now I'm working as a cloud engineer.
>
> Thanks for your interest in KernelCI.
>
> > Would like to start contributing as a build and boot tester. I've a
> > Raspberry PI 3 with ARM Hardware, and a computer with an Intel Core 2
> duo.
>
> Currently, a single Core2 duo won't be very useful to us as an extra
> builder, and we already have rpi3 boards in a few of our existing labs.
>
> However, if you'd like to setup your rpi3 into a LAVA lab to better
> understand how KernelCI lab works, and potentially add more hardware, I
> suggest following our docs for setting up your own LAVA[1]. That doc
> doesn't (yet) mention it, but you we now have a dockerized version of a
> LAVA lab that hopefully simplifies the learning curve of setting up
> LAVA: https://github.com/kernelci/lava-docker/
>
> Kevin
>
> [1]
> https://github.com/kernelci/kernelci-doc/wiki/Setting-up-a-local-development-instance
>
[-- Attachment #2: Type: text/html, Size: 1839 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-03-23 22:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-03-17 22:42 Contribution as a build and boot tester Javier Romero
2020-03-23 22:31 ` Kevin Hilman
2020-03-23 22:41 ` Javier Romero
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox