The master git repo for kdevops is:

• https://github.com/linux-kdevops/kdevops

kdevops provides a framework for Linux kernel development and testing. It makes use of local ansible roles and optionally lets you use vagrant or terraform. kdevops is compatible with Linux in a distribution agnostic manner and has support for OS X as well. It aims to provision nodes and tooling for kernel development in a flexible, configurable and speedy manner.

To give you an idea of the power and goals behind kdevops we provide a few quick demos of what you can do below. More workflows will be added with time. Additional documentation detailing how to get started as well as how to add new workflows follows the quick demos.

Configure kdevops to use bare metal, cloud or a local vm based solution, pick your distribution of choice, enable the Linux kernel workflow, select target git tree, and get up and running on a freshly compiled Linux git tree in just 4 commands:

• make menuconfig
• make
• make bringup
• make linux
• make linux HOSTS="kdevops-xfs-crc kdevops-xfs-reflink" for example if you wanted to restrict running the above command only to the two hosts listed

To test a kernel against fstests, for example, if you enable the fstests workflow you can just run:

• make fstests
• make fstests-baseline

To test a kernel against fstests, for example, if you enable the blktests workflow you can just run:

• make blktests
• make blktests-baseline

We have a public chat server up, for now we use discord:

• https://bit.ly/linux-kdevops-chat

It is best to think about kdevops in phases of your desired target workflow. The first thing you need to do is get systems up. You either are going to use baremetal hosts, use a cloud solution, or spawn local virtualized guests.

The phases of use of kdevops can be split into:

• Bring up
• Make systems easily accessible, and install generic developer preferences
• Run defined workflows

Below is kdevops' recommended documentation reading.

• kdevops requirements
• kdevops' evolving make help
• kdevops configuration
• kdevops first run
• kdevops running make
• kdevops running make bringup
• kdevops example workflow: running make linux
• kdevops running make destroy
• kdevops make mrproper
• kdevops pci passthrough configuration

kdevops supports its own kernel continous integration support, so to allow Linux developers and Linux distributions to keep track of issues present in any of supported kdevops workflows and be able to tell when new regressions are detected. Documentation for this follows:

• kdevops kernel-ci

Below are sections which get into technical details of how kdevops works.

• Why vagrant is used for virtualization
• A case for truncated files with loopback block devices
• Seeing more issues with loopback / truncated files setup
• adding a new workflow to kdevops
• kconfig integration
• Motivation behind kdevops
• Linux distribution support
• Overriding all ansible role options with one file
• kdevops vagrant support
• kdevops terraform suppor - cloud setup with kdevops
• kdevops local ansible roles
• Tutorial on building your own custom vagrant boxes

This work is licensed under the copyleft-next-0.3.1, refer to the LICENSE file for details. Please stick to SPDX annotations for file license annotations. If a file has no SPDX annotation the copyleft-next-0.3.1 applies. We keep SPDX annotations with permissive licenses to ensure upstream projects we embraced under permissive licenses can benefit from our changes to their respective files. Likewise GPLv2 files are allowed as copyleft-next-0.3.1 is GPLv2 compatible.