Currently, the SUMA test-suite takes about 6 hours to complete, often fails in the first tests, which set up the environment for the rest of the tests, those tests are what we named "core features".

There are attempts to solve some kernel deadlock with using lockless printk ringbuffer. The proposed implementation is pretty complex (6 stages, 6 write and 6 read barriers, two buffers, entries linked via list, ...)

Try to prototype an interactive dashboard for parts of the data available on SMELT.

motivation

As an openQA contributor I could learn from openSUSE release managers how the overall process can be improved.

The goal is to run the Elastic Inference Demo managed by kubernetes on a Raspberry Pi4 Cluster with openSUSE Kubic.

This hackweek I'll be working on Kanidm, an IDM system written in Rust for modern systems authentication. The github repo has a detailed "getting started" on the readme.

Project here: https://confluence.suse.com/display/AAI/HackWeek19 Will keep working out of HackWeek as "best effort" personal project to make it evolve and keep learning.

There are multiple reasons for this project. First, I want to re-cap my ruby programming knowledge. Secondly, this course is available on pluralsight. This is project for 1-day, where I plan to continue and create some project and dive a little bit deeper into it.

Goal:

You can encrypt your servers root filesystem, but need to provide a password during the boot process in order to "unlock" and start the system. This is easy if you have physical access to the server by entering it via keyboard. But if you do not have physical access it's not that easy.