Image Mode Support in Testing Farm
summary
Image mode testing for RHEL/Fedora/CentOS Stream runs in Testing Farm using tmt and bootable container files that are converted to AMIs; to avoid a 20+ minute per-run bottleneck images are prebuilt AMIs cached in AWS and daily rebuilt, stored in a container registry, and requested via the Testing Farm API. tmt performs on-host image rebuilds and reboot cycles so tmt bootswitch rebuilds container images and reboots to reach the desired state. Users can reserve image-mode VM in ~5 minutes and re-run existing tests; first-boot fidelity uses bootsy conversion (nested-virt path exists but is less scalable).
AI-written summary · about
chapters (8)
- 0:00Testing Farm and Image Mode
- 6:31Package Mode pipeline
- 9:02Image Mode challenges
- 11:31Image Mode workflows
- 16:08First boot in Image Mode
- 21:06Image Mode in Fedora/CentOS CI
- 23:55Reserving Image Mode systems
- 26:50Q&A on Image Mode
related talks
25mIdentical Testing Environments from Laptop to CI with tmt and Testing Farm
35mBoost your testing with Testing Farm
21mAutomated OS Testing Using Containers
48mFedora Automated Testing State of the Art: Not Quite CI for Distributions, but...
51mWrite tests for the Always Ready Operating System
37mVirter – How the "Docker for VMs" Can Help You Test the Linux Kernel
31mTest Automation For Mainframe Applications
26mTesting Github PRs on Fedora/Centos with Packit