Learn the inner workings of TCP as implemented in the Linux kernel. This will involve * reading textbooks and IETF docs

It's not always straightforward to open a core dump originating from customer's environment, since there's a wide variety of versions of all the binaries involved - usual workflow is to install a VM with the SP that the customer is using, enable debuginfo repositories and then follow the buildid hints that gdb is providing. However this sounds like a bit of an overkill. Lately, there has been a debuginfod project announced:

Problem description Jira is used inside SUSE to track various process/workflows.

This is kinda continuation of my last hackweek project - learning python3 the parcical way. The goal is again to replace existing bash script which will generate 3 node KVM HA cluster on my workstation and automate quite a boring part of HA regression testing.

Since SUSE Manager doesn't scale out and stacking it into another pyramid of susemanagers won't help here, the real architectural changes needs to be done to achieve true scale-out of this product. This hackweek project is about how to Turn SUSE Manager into a cluster. Areas to be tackled:

Last hackweek filtra was created – a tool to extract information like lead and cycle times from Github repos for (but not limited to) projects that are doing Kanban. The collected metrics can then be visualized with Grafana. Currently there are two problems with filtra:

Features I'd like to implement: * Built in search on obs, with one-click branch checkout,

I own a 3D printer / Anet AM8 / and after 1,5y its time to upgrade the electronics, mainly the stock motherboard and get it ready for multi-color printing. Also the time has come where I would like to not only download 3D models from thingiverse but also create or customize the models for my usage. Plan is to:

The project aims to port openSUSE to the ROCKPro64. The ROCKPro64 is the most powerful Single Board Computer released by Pine64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a MALI T-860 Quad-Core GPU.

I'd like a way to have a device on my desk which lights up to indicate that I have something I should be paying attention to. Initially, I'd like this to be for Office365 calendar events and GitHub mentions, but ideally it should support arbitrary messages. The plan is to assign specific colors (ideally "patterns" consisting of a sequence of colors and time) to specific message types. I have a handful of raspberry Pi Zeroes, a couple of OLEDs, a strand of individually-addressable RGB LEDs, a power supply, and some misc electronics (like the 3.3-5v logic level shifter necessary for the 5v LED strand). I'm thinking Python is probably the way to go for the software. I'm hoping OpenSUSE actually works on the Pi zero. :D If not, there's an ESP32 with a built-in display and a few Pi 3s laying around barely used, maybe one of them will work.

Although CNCF projects are almost exclusively related to Linux containers, some ideas, like wrapping all the services into network proxies to create a distributed data-plane and enable true observability, could perhaps be explored for some kind of backport in complex legacy distributed systems, like... say... S4/HANA?! I don't even know if this is feasible, but trying won't hurt... just stand at a safe distance from the cluster!

Currently we have two sponsored 3D printers available in the Nuremberg office. Both are located in a lab - which makes it hard to access them. Both also need some (hardware) maintenance. This (hopefully short) side project should make the printers more usable and accessible for others.

This hackweek I will focus on improving my drawing/painting skills. I will do either some portrait for people I know at SUSE and this could be used as Github profiles or do something related to Linux/SUSE chameleon etc. ( without any precise goal).

The idea here is to study and understand how ephemeral storage for containers works and investigate if local storage could be avoided at all and Ceph used instead. Could new storage driver be developed to support Ceph storage:

• implement a POC deploying CaaSP v4 on top of AWS using: Spotinst's elastigroup
• "Spotinst Elastigroup predicts Spot Instances behavior, capacity trends, pricing, and interruptions rate. Whenever there’s a risk of interruption, Elastigroup acts accordingly to balance capacity up to 15 minutes ahead of time, ensuring application availability.

OSC is already available on Homebrew, but it is missing the integration with Staging as the openSUSE-release-tools are not available. In this Hackweek project I would like to get the openSUSE-release-tools running on macOS via Homebrew.

Using the camsource and vlc packages as an example. If camsource is configured to use a given dev/video[n] device with a choice of resolution in the width and height fields of a camsource conf file then if camsource is the first application to access the device captured images are as-expected. However, if an application like vlc is used for the same device (and exited) before starting camsource (e.g. to check the view from the camera before starting camsource) and if the camera supports higher resolutions than used in the camsource configuration what occurs is that camsource will not setup the camera to use the configured resolution and has a broken view of the camera output based on the vlc chosen resolution chopped to the camsource configuration. For example, with camsource configuration set to use 640x480 on a camera that supports 720x480 and vlc is used and exited before camsource is started then the captured camsource images contain two non-continuous partial image blocks with a horizontal border dividing them. I assume either vlc fails to fully reset the device configuration when exiting or camsource fails to initialize the device "from scratch" when starting. The two applications use different video device APIs but the setup and cleanup for the camera in each case is a very limited part of the application's functionality.

There's a long standing request to extend the output of dmidecode to something that would be machine-readable. Something like an XML or JSON-based format. Unfortunately this can't be implemented right now because the output of dmidecode is generated by open-coded printfs as the DMI table is being parsed, with no intermediate structures nor temporary buffers. While implementing a machine-parseable output is out of scope for a single hack week, let's remember that even the longest journey starts with a single footstep. I would like to try and rewrite the 5200 lines of code of dmidecode in such a way that printing the output would be somewhat separated from parsing the DMI table and done by a limited set of dedicated functions. Alternative output formats could later hook into such functions.

Termux is already bringing a terminal and debian package manager to Android. Let's see if we can reuse it and provide a base system with zypper and build openSUSE:Factory for it in OBS.

Background

Given the number of different demands on our time and attention, it becomes increasing hard to focus and find the 'flow state' where a developer can be most productive. Interruptions due to chat notifications, email, and updater applets all break focus. Additionally, the desktop metaphor has in most cases failed to evolve as the browser and other MDI interfaces have become the focus for many users, and increased performance has allowed us to keep more tasks running and present on the desktop at once, presenting a higher cognitive load to the user.

I would like to learn more about something outside of engineering. I have selected to learn more about marketing; something our overall team is doing more of...

Since Kubernetes already has a clear path of "in-tree" volume plugin to CSI migration. I would like to understand the concept of CSI with writing a simple driver for Kubernetes. Reference:

Simplify, modernize, and accelerate the process and tools for reviewing YES submissions from partners. Hopeful goals to accomplish:

Provisioning works with Autoyast/Cobbler for traditional clients, with profiles to enable major version upgrades. The goal is to offer that in a predictable way that can be scheduled and automated for salt minions. Salt minions pose a different challenge, and we would like to enable a reboot into the upgrade without needing PXE not traditional client to enable it.

Create a prototype of an agent on kvm hosts to control the distributen of master / worker nodes between different kvm hosts. No central control plane should be used - the main design goal should be: as simple as possible :-)

Whether it's building a newer, upstream UBoot, EDK II, or merely a SLE based rootfs, I want to make this platform a realistic possibility for desktop, digital signage, labs, etc.

Build and benchmark some smaller SES clusters (2 - 3 nodes) targetted at edge deployments. Evaluate the performance and configurations.

During the previous Hackweek [0], I have successfully implemented, tested and merged [1] an implementation of the entire C++ standard header <future>. This time, my aim is to modernize the C++14-esque standard library [2] of HelenOS [3][4] with a C++17 feature - the <filesystem> header. The <filesystem> header is much larger than the <future> header which I barely managed to implement and test in the allocated time for the previous Hackweek, but <future> was mostly OS-independent as it relied only on previously implemented features of the standard library. The <filesystem> header, however, is limited by the filesystem API of the OS and as such implementing of the entirety of it might not be possible, limiting the scope of the project (which is a good thing due to the time constraints). The primary features of the header [5] that should be implemented:

labgrid [0] is an embedded board control python library with a focus on testing, development and general automation. It includes a remote control layer to control boards connected to other hosts. My idea was to use this to be able to test my MediaTek boards remotely.

The USB controller (Via Labs 805 XHCI) on the RPi4 sits behind a PCIe bus which has no drivers at the moment in u-boot. After implementing it, we'll also have to make sure the USB HID is correctly connected with UEFI routines.

Picotm is a system-level transaction manager. It provides transactional semantics to low-level C operations, such as modifying data structures, (some) file I/O, memory access. Picotm also handles error detection and recovery. It's fully modular, so new functionality can be added. For the Hackweek, I want to dedicate some time to picotm. I want to finish some of the refactoring work that I have been working on. If there's time left, I'd like to investigate two-phase commits and how to support them in picotm.

Intro

L3 bug load is a concern in the SUSE Manager Development Team, and we want to do something about that.

Currently it's pretty difficult to create tests for some specific package. So something like TravisCI for OBS would be good.

Goals * get used to some of this ugly buzzword tools as they are used in a broad audience

Having done only very little with openQA in the past I would like to learn more about it. I would like to start writing a test suite for profanity.

zypper in wireguard-tools Did a Debian OBS build: https://build.opensuse.org/request/show/712261

My previous knowledge about Python is small. I need learn more about python. Using a script write in shell script, andt this script already ported to python by a collegue team. I'm going to use a port of this script to understand and maybe collaborate with this code.

The plan is to implement a safe path resolution library for Linux to avoid the plentiful numbers of security vulnerabilities that have been seen in the wild related to path resolution race conditions and various other attacks. I've been working on kernel-space solutions but even if they were merged, it is difficult to use them safely directly. So this library intends to provide simple wrappers that everyone can use. https://github.com/openSUSE/libpathrs

People are interested in Linux on Windows via WSL, especially given the new fully virtualized Linux kernel in WSL 2. It's interesting to know whether registered SUSE installations might be running in WSL as opposed to other Microsoft virtualization platforms, but the current approach taken by SUSEConnect (the client for SUSE Customer Center) does not permit this.
By inspecting the contents of /proc/, it is possible to tell these platforms apart. This project aims to enhance SUSEConnect to do so.

This is a side project I started a while ago. The idea is to implement a tagging engine with some "advanced" features for the Django web framework (in what Django calls a "reusable app"). I have many ideas for possible features, but the most basic are inclusion and exclusion relations between tags.

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:

QDirStat in General

See QDirStat project page at GitHub