There seems to be an overall consensus that the ioctl interface used by ethtool is a poor design as it's inflexible, error prone and notoriously hard to extend. It should clearly be replaced by netlink and obsoleted. Unfortunately not much actual work has been done in that direction until this project started.

Customers are using complex storage stacks such as LVM over dm-crypt over MD RAID over multipath over iSCSI and FC with LOTs of LUNs, and we're facing problems in that area which are usually very hard to reproduce. It's also hard to guard against regressions.

Lately the necessary patches to get rudimentary support for the Mediatek chromebook with a mainline kernel got posted. There are some hacks and I'll work on some good solution to get graphics go, at least.

I would like to learn Elixir, I plan to do some tutorial and look into books. I if I have time also start with Phoenix the framework for Elixir

Ai and Machine learning play important role in our life, I'd like to learn it.

There are many fun peripherials that you can connect to a RPi but PC users are not left out either

Try to get back an automatic email notification about new or changed SAP Notes. Since SAP has closed down some of their internal servers, which hosted an unofficial database/API to the SAP Notes, the nice email notification service of the SAP LinuxLab is terminated.

Idea is to have SUSE system with OpenZFS as root FS.

I have been known to talk anybody I held presentations with into using odpdown.

What is the VFX Reference Platform? https://www.vfxplatform.com/FAQ/

To ease debugging cgroup relates issues this suggests to:

In the past, some customers ever complained that OCFS2 file system performance went down when listing a big directory (e.g. include 400k files). According to my preliminary investigation, this performance problem is related to file system block allocation algorithm. Then, I want to look at the current mainstream file systems (e.g. EXT4, XFS, etc) block allocation algorithms in this hack week, compare and analysis these algorithms advantages/disadvantages.

Currently, way we distribute ssh keys within QAM on our testing infrustructure is a bit cumbersome - maybe we should try to (ab)use existing salt used by our internal infra team.

The current GUI of FriCAS is ancient and difficult to use. I plan to improve that by using modern GUI frameworks, at least to make a working proof-of-concept demo to show this idea works.

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.

Hackweek 21?

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.

It ain't rocket science, it ain't thrilling, it's just useful.

This can be seen as a subproject of ethtool netlink interface but from the technical view it's independent.

Exactly what problem will this solve?

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.

During the previous Hackweek [0], I have successfully implemented, tested and merged [1] an implementation of the entire C++ standard header . This time, my aim is to modernize the C++14-esque standard library [2] of HelenOS [3][4] with a C++17 feature - the header. The header is much larger than the header which I barely managed to implement and test in the allocated time for the previous Hackweek, but was mostly OS-independent as it relied only on previously implemented features of the standard library. The 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).

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.

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

• implement a POC deploying CaaSP v4 on top of AWS using: Spotinst's elastigroup

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

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:

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.

This hackweek I will focus on improving my drawing/painting skills.

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?!

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.

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.

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.

Features I'd like to implement:

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.

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.

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.