Red Hat contributes to stabilizing the upstream linux kernel using its Enterprise class hardware. For many years, this hardware has been managed through Beaker, a software for managing and automating labs of test computers. Beaker is used often, especially when testing different architectures and special hardware.
However, in some cases, for example when generic x86_64 devices suffice, it is easier to take advantage of stable infrastructure of different providers. As providers appear, evolve their services and add non x86_64 hardware, it is suddenly important to be able to target these providers for running tasks and scaling-out testing.
Once a system is up, a testing harness called restraint allows a relatively low-level and lightweight way to ensure tasks are executed. Beaker has used this harness for some time. It fulfills important requirements for kernel testing, such as being reliable, being able to handle machine reboots and more.
Because of CKI (Continuous Kernel Integration) team's need to scale-out to different providers, I've written UPT project (Unified Provisioning Tool) to simplify provisioning and Restraint Test Runner take advantage of restraint for (kernel and non-kernel) test running.
This talk will briefly discuss current approach towards running (primarily kernel) tests and targeting different cloud providers.
This talk will discuss the aforementioned tools, their capabilities and features to execute tasks, run tests, simplify test result interpretation, provide partial test results and handle unexpected behavior.
As different tools in the open source community evolve as well, we will also discuss possible cooperation, as this is already on the radar.
We encourage you to share and invite people who might be interested; this talk is suitable for anyone in kernel testing/tools, CI and related topics.