In ubuntu, you can install grub-ipxe, which adds an ipxe entry to the grub menu. This allows you to easily pxe boot on machines that may not natively support it. You can also use it along with grub2-reboot to remotely re-image a machine. The project has been started here: https://build.opensuse.org/project/show/home:blarson:grub-ipxe It needs to be tested, and polished before trying to include it into opensuse.

Create a JUnit test suite for Firefox browser and integrate the tests into SLEnkins.

https://github.com/MalloZup/go-verdura

The AverMedia LGP Lite (GL310) is a cheap HDMI (with pass-through) to USB 2.0 capture card. The card only supports compressed output (afaik) which makes it slightly less useful but still very valuable when debugging graphical issues. The plan is to hook a few of these up to my test machines so I can stream the output to my workstation and integrate with the rest of my test setup. So far I've discovered that the card needs to be loaded with two firmwares. One for audio and one for video. Hopefully this will turn into a standard UVC device once the initial bootstrap is done fingers crossed. Specifications (From AverMedia webside):

I wanted to work on something test related this hackweek since we always need more automated testing of our virtualization-related packages. There are many possible test-related topics, but I think a good addition would be more unit tests that are run during build time, e.g. during 'make check'. Additional tests of this nature would then be run by upstream developers and the various distro CI setups, exposing the tests to more environments than would typically be available within SUSE. To this end, I'm planning to add unit tests to libvirt.git that test conversion of domain XML to structures used by Xen's libxl interface. The first attempt at such tests was nearly 3 years ago

Having worked on KVM for a long time, it's time I actually start using it myself! I now have a high enough powered laptop to have a permanent setup on my laptop to do almost all the testing needed for releases, as well as maintaining playgrounds for upstream work and involvement. This will include nested virtualization, which is getting pretty bulletproof in latest kernels, as well as being able to play more with these other architectures that we now support KVM on, via improved TCG emulation (of course some testing and development will always rely on the physical hardware, but still a lot can be done via TCG incl. user-linux mode. I'm also seeing which aspects of pass-through testing will make the most sense to perform on the laptop (pci, usb, video, filesystem, etc.). Hopefully at the end of the week I will have gotten a better feel for all aspects of KVM as a "power user', and not just as a developer.

Overview

From the kernel-source git repository for SUSE kernels we can extract the people who backported a patch and the files a patch touches. Use this information to build a database for which paths are touched by which developers and write a tool to find the most relevant people for a given source path or upstream patch.