The CRUSH algorithm determines how to store and retrieve data by computing data storage locations. CRUSH empowers Ceph clients to communicate with OSDs directly rather than through a centralized server or broker. With an algorithmically determined method of storing and retrieving data, Ceph avoids a single point of failure, a performance bottleneck, and a physical limit to its scalability. CRUSH requires a map of your cluster, and uses the CRUSH map to pseudo-randomly store and retrieve data in OSDs with a uniform distribution of data across the cluster.

Translations get more and more important in packages live.

Project Description

Building on top of Rouslan Dimitrov's Microcontroller Class D Amplifier, I developed the idea to feed the power amplifier with PCM data directly. Rouslan does some dithering and noise shaping, but I'm convinced that proper interpolation would sound better. The ATtiny is too slow to do even cubic interpolation so I'll move that into the host.

I have my favorite card game from childhood . Unfortunately description is available only in Russian https://uk.wikipedia.org/wiki/%D0%94%D0%B5%D0%B1%D0%B5%D1%80%D1%86%D1%8C . Currently my friends spreed across the globe and here in Germany no one except my wife knows the rules . I would like to to have ability to play this game with my friends like I did in school/univercity.

In the previous hackweek (14), the following objectives from project "A generic mechanism for analysing and manipulating diverse software configuration files" were worked on:

If you are now thinking of Salt-SSH, this is not completely wrong, but also not right. What we are talking about here, is an other Transport for Salt, a replacement for ZeroMQ.

Setup and operate a Mode-S Beast that receives the ADS-B broadcast signals sent out by airplanes.

Description

In our team, we currently manually deploy our Terraform code (namely, the SUSE Registry at registry.suse.com) from our own PCs. This is error prone, as it would be very easy to override something by mistake. I want to create the appropriate .gitlab-ci.yml file that will:

This project aims to run VMs in a CaaSP 4 cluster using kubevirt and a libvirt+qemu container (aka compute container) based on SLES15 SP1/2. Compute containers based on openSUSE Leap15.1 and SLES15 SP1 already available in registry.opensuse.org and registry.suse.com respectively. VMs can be deployed to the cluster but there are several functional problems that need investigating, e.g. accessing the VM's serial and VNC consoles, proper network access, etc.

Starting with CUPS 1.6 things have changed considerably. Clients are no longer discovering broadcasted printers anymore. Distributions (e.g. Debian) has backported the original protocol into cups-daemon package but this doesn't seem to work either on my laptop. I would like to look and try to understand what the hack is going on here.

Description:

This issue has been blocked for a while due to time constraints so I want to take Hackweek 19 to work on it.

Project Description & Goal

The GPD Win is a Nintendo 3DS XL sized PC featuring a keyboard and gaming controls. Having openSUSE working on it would be great, unfortunately Tumbleweed doesn't work at all on it and Leap 42.2 is lacking many important features.