Few weeks ago whilst analyzing the possibility of using Terraform[1] via terraform-libvirt [2] plugin, I came across Terratest [3], which is an automated testing framework. My initial thoughts have been written here [4] but I'd still like to check out Terratest in more detail.

Learn Rust by following The Rust Programming Language book.

So far the style (color, shape, ...) of the devicegraph output of libstorage-ng is hard-coded. The user of the library should somehow be able to customize the style.

Following the work started in the last hackweek, Improve OBS service scripts, I will try to migrate current service script for workers to systemd unit, and at the same time, try to get rid of the sysv code.

Create a sound board that has the following requirements: * Works in Browser

The idea is to have a friendly way to access live cluster's nodes, compare outputs of simple commands and find out differences in tables data / structure. Current state: implemented and tested scripts which split table into ranges and then for each range check rows count and rows checksums.

When all of the SUSE Manager squads switched from SCRUM to a Kanban we lost estimations and therefore also the ability to do predictions. But there are other ways to get insights that are even more reliable, since they are based on anecdotal data. The lead and cycle times of issues are the two most important here. I'd like to extract those two for all of the issue from the spacewalk project and explore how they can be visualized in meaning- and helpful ways.

Create a new generic CUPS wrapper backend /usr/lib/cups/backend/monitor that runs in parallel with the actual backend to monitor it.

Following trademark and licensing issues with Grafana, explore the possibility of debranding Grafana and use that in SUSE Manager (and maybe others) Products are available from GitLab: https://gitlab.suse.de/susana

At SUSE Manager and Uyuni we use right now a set of bash scripts called sumaform-test-runner to run terraform and cucumber, send notifications and store cucumber results. However such scripts are currently hard to maintain and extend, and bash is clearly showing it's limitations when it comes to parsing cucumber results, working with JSON stuff, or using APIs. Besides it forces us to have credentials hardcoded at the main.tf files, which is a huge problem for making a public CI for Uyuni.

We've (mostly @cbruckmayer) put a significant amount of time into our performance measurement dashboards based on influx/grafana. I want to share this with the world because it's most awesome and easy to use. It's also nice if people don't go to some PaaS provider just for this...

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". To solve this problem we had planned to move from Jenkins Job to a Jenkins Pipeline, having stages to split the test suite into core features, initialize clients, secondary features. So,if one stage fails, the rest of the stages will not be executed.

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, ...) I have a idea how to make it easier with tracking the state and sequence number in one atomic variable. It might allow to remove the lists and many barriers. It is possible that it will just not work. Let's see.

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

Background

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. * The openSUSE Kubic image should configure itself correct at the first boot with ignition.

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. Kanidm Github

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. Here is the url for anyone interested: https://app.pluralsight.com/library/courses/code-school-rails-for-zombies/table-of-contents

Goal: I'd like to have the release process defined in markdown/git and use it as a source for process creation in redmine.

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. This project is about to set up a server that might be able to have an encryted root filesystem which can be "unlocked" by entering the password via ssh.

The ESP8266 is a low-cost WI-Fi microchip with full TCP/IP stack and microcontroller capability. I want to explore the features and (in case of success) attach a BME280 to get temperature, humidity and barometric pressure information streamed over WI-Fi. As the price of both components is just around 10 EUR, this would be a nice add-on for my weather station at home...

Create a gnome-shell extension inspired from an Android app floating toolbox. floating toolbox

I want to create an exporter for a X instagram profiile using the Instagram API. The exporter should export some metrics on my user and then I can build perhaps some useful dashboard

I'm building a web-site for my drawing/painting things. This hackweek project I want to do more frontend related stuff like javascript/clojurescript and html for improving the layout and so on of the page.