Learn Go language by through The Go Programming Language book.

This is a task to update current WSL-Launcher (which can be already buildt in OBS) with latest-greatest upstream code https://github.com/Microsoft/WSL-DistroLauncher Fork of fabian's project (initial work to get it working):

https://github.com/dmulder/phylogen As part of a graduate project I created the phylogen script, which combines the ASTRAL and IQTREE analysis tools into one iterative approach to finding the highest bootstrap score tree for various species of Mayflies. At the completion of the project, there was some work left undone, and I had a few ideas on how to improve the average bootstrap score of the final tree.

My goal is build on Alberto's work on "yomi" and the new Salt-based virtualization management features that Cedric has contributed, then combine them with a Redfish prototype to do the following from one (ideally idempotent) Salt state (orchestration state if required): * mount the installation media via Redfish

Since quite a while I'm interested in learning the programming language golang. I want to use the time to get a basic understanding and maybe realize a small project with the gained knowledge.

Ceph offers a highly scalable and fault-tolerant storage system. Samba is already capable of sharing data located on the Ceph Filesystem, however scale-out sharing (the same data exposed by multiple Samba nodes) currently requires the use of CTDB for consistent and coherent state across Samba cluster nodes. In such a setup CTDB provides a clustered database with persistent key-value data storage and locking. Database usage is abstracted out via a generic dbwrap interface. Ceph's librados library provides an API for the storage and retrieval of arbitrary key-value data via the omap functions. A watch/notify protocol is also provided as a mechanism for synchronising client state (locking). Key-value data stored in the RADOS back-end inherits the same redundancy features as regular objects, making it a potentially good candidate as a replacement for CTDB in scale-out Samba clusters.

My music manager, Bard, was improved in the last hackweek with a very simple React-based web interface but I didn't like the result at all (basically, after learning React I noticed I didn't like it and all the dependencies and the complexity it added) so since then, I've reimplemented the web interface using just jQuery. Also, in the last months I've added musicbrainz data structures to the database (which was also ported to use Postgresql) to prepare bard to use MusicBrainz's data. I also stopped using other python libraries to read audio files and use the ffmpeg libraries directly instead with a c++ wrapper implemented inside Bard which is much much faster. In this hackweek I'll try to finish the integration of Bard with MusicBrainz (basically, import the needed MB data to the database) and use it to generate a web interface that shows and uses that information to organize music. This would allow to show information and for example perform searches for songs not only on the main artist but also on performers or even mixer (see for an example all information available on this Queen album)

The day has come to finally merge more and more apps into one single place, and this time it shall be externaltools. I'd like to merge functionality of externaltools into geekos, as they share quite a lot of concerns. This way, we can beat fragmentation and have a single tool to track teams, tools and floors.

Circuits is a coding marathon to challenge developers with several programming questions of varying difficulty level over 9 days. https://www.hackerearth.com/challenges/competitive/june-circuits-19

This is my attempt to catch up on the field of machine learning. In order to not "waste" time of exercising with dummy data the Security team came up with a couple of interesting questions: 1. Is a software mentioned in a bug or security issue relevant in incident management (Tagging as Not for us)?

The goal of this project is to create video tutorial describing configuration of SUSE Manager for Retail. There is a precise documentation describing every step of its configuration, but SUSE Manager for Retail is still a very complex piece of software and there is a lot of things to be configured configured properly (proxy configuration, Kiwi image building, DNS, DHCP, etc.) in specific order to get it finally working.

As the automation became a standard within Maintenance QA work, I would like to became more familiar with the whole magic behind. Plan is to go through internal docu a try to setup openQA and write some simple tests (and adjust the docu once there are any gaps): https://confluence.suse.com/display/openqa/QAM

Goal is to implement a rados backend in drivers/nvme/target. That will allow the NVMe target implementation to directly access Rados objects (ie export RADOS objects as namespaces), allowing third-party applications and/or OS to use NVMe-over-Fabrics to access a ceph cluster.

Stream Radio device - It is built with Raspberry Pi Zero WH

Short-term:

1. Understanding of docker knowledge

In the other day, there were questions about to migrate high availability solution into OpenStack. With that context, there is no question to run the critical pacemaker and corosync processes inside the cloud. There is no difference between VMs and bare-metals in regarding to the dependency management system for both systemd and pacemaker, which is quit different than the situation of the container world. However,

The monitoring in our internal infrastructure needs some love and attention. I want to spent some time during this hack week on the monitoring by fixing old checks, implementing new checks and making sure that those are configured and installed via configuration management. Checks I have in mind for instance are: