Repository navigation
Enable Qualcomm lab for new KernelCI infra #358
Description
Qualcomm wants to bring their lab to the new KernelCI infra. Let's use this ticket to drive the discussions.
@EmbeddedAndroid what tech are you using for the lab? LAVA? If it is LAVA, it should quite easy as we support that runtime already. If it is something else, we can walk you through how to implement the runtime. (doc for all this is in the works).
API token request: #357
Metadata
Metadata
Assignees
Labels
No labels
Activity
EmbeddedAndroid commentedon May 13, 2024
@padovan We are using LAVA, our public instance can be found here: https://lava.infra.foundries.io/scheduler/
JenySadadia commentedon May 14, 2024
Hi @EmbeddedAndroid
To enable Qualcomm lab in KernelCI, we would need a lab token and its description.
Please have a look at https://github.com/kernelci/kernelci-pipeline/blob/main/doc/connecting-lab.md#token-setup.
Could you please create one for KernelCI?
EmbeddedAndroid commentedon May 14, 2024
Hi @JenySadadia
Sure no problem, I'm going to loop in @mwasilew as he is our lab admin and will generate on our behalf.
Many thanks!
EmbeddedAndroid commentedon May 15, 2024
@JenySadadia we have generated the token and description, shall I email to you or is there another method you'd prefer?
A more generic question, is there documentation on how LAVA jobs are generated with the new infra? We are trying to get our heads around if we need to do this now, or it will be provided by the KCI project.
pawiecz commentedon May 15, 2024
@EmbeddedAndroid I can't point you to the docs but let me give you a quick overview:
Templates for submitted LAVA TestJobs are currently split between two repos (to be merged in the future):
Former ones in many cases (baseline, kselftest, sleep, tast) set up values for rendering final TestJob definitions, latter ones contain LAVA-specific sections.
Basic example (
baseline-arm64):baseline.jinja2template to set up required values) will be triggeredboot_methodand test steps templatesHere is a node example of such a job with corresponding LAVA TestJob
mwasilew commentedon May 15, 2024
@pawiecz Do I understand correctly you will still be submitting jobs to the LABs (push)? I was under impression the new architecture asks labs to pull the events and submit the jobs themselves.
padovan commentedon May 15, 2024
@mwasilew you can do both. See #349 (comment) for the pull example.
pawiecz commentedon May 15, 2024
@mwasilew to complete the picture: TestJobs are pushed to the LAVA instances and the event activation (pulling) is used internally by sub-services.
mwasilew commentedon May 17, 2024
@pawiecz ok, so there is no difference comparing to the "old way". There is still no way to enroll with lava server behind firewall.
JenySadadia commentedon May 18, 2024
Hi, you can send me on IRC. My nickname is
jenysadadia. Thanks.pawiecz commentedon May 28, 2024
@mwasilew short follow-up about verifying if LAVA TestJob templates render expected definitions:
after setting up core environment and moving all templates (including
config/runtime/*from-pipelinerepo) into-core'sconfig/runtimeyou can use the existing Node to rerender TestJob definitions.Example:
config/runtime./kci job generate -c ../kernelci-pipeline/config/pipeline.yaml --runtime=lava-collabora 6653735bce5c0068e1b06921to render definitionspadovan commentedon Jul 5, 2024
can this issue be closed? It seems the lab is already enabled.
mwasilew commentedon Jul 5, 2024
It's getting jobs from staging kernelci. How do we migrate it to production instance?
nuclearcat commentedon Jul 8, 2024
I will schedule on this week moving most of tests to production
mwasilew commentedon Jul 8, 2024
I guess we can close this ticket then.
nuclearcat commentedon Aug 31, 2026
Closing as completed. Qualcomm/Foundries LAVA support was merged in kernelci-pipeline PR #612, the current production configuration still contains the
lava-foundriesioruntime, and the lab maintainer explicitly confirmed in this thread that the ticket could be closed.