LKFT Remote Labs
summary
Proposal and prototype for LKFT Remote Labs extend Linux Kernel Functional Testing to member SoCs using Git, Docker, Jenkins, Lava/Jenkins/Squad and a Raspberry Pi relay with powered USB hubs and PDU control. Three hosting models are defined: partially hosted, fully hosted and ultra secure (all artifacts and results can stay behind a firewall). CI pipeline hits a claimed 48 hours commit→results target (sustained three months), demo runs successfully (LEDs blink in ~6–7 minutes, emails and dashboard reports produced) and code is on GitHub.
AI-written summary · about
chapters (21)
- 0:00Introduction to LKFT Remote Labs
- 1:04What is LKFT and its mission
- 3:31Benefits of LKFT for downstream vendors
- 4:33Current LKFT operational capacity
- 7:02Remote Labs concept explained
- 8:29LKFT overview and toolchain
- 10:35Jenkins and system image creation
- 11:19Job scheduling and test execution
- 12:02Reporting and dashboard features
- 13:25Curation and triage process
- 14:05Hardware selection criteria
- 16:14Expanding LKFT with member hardware
- 17:38Member benefits of remote labs
- 20:08Privacy and security in remote labs
- 21:10Demo introduction by Chase Qi
- 24:02Hosting options for remote labs
- 28:43Hardware setup for remote labs
- 30:14Getting started with remote labs
- 31:41Contacting Lenovo for remote labs
- 32:32Demo results and reporting
- 34:22Future challenges and solutions
related talks
41mKeeping up with LTS: Linux Kernel Functional Testing (LKFT) on Devices
46mLinux Kernel Functional Testing, or How to Build and Test Millions of Linux Kernels
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
27mFaster Linux Kernel Testing with Linaro's Open-Source Tools and LKFT Automation
43mAutomated Testing & Board Farming
26mLAVA + OpenQA = Automated, Continuous Full System Testing
48mBoard Farm APIs for Automated Testing of Embedded Linux - An Update
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto