YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project.

I tried to work blockchain into this, just so we could cover the trifecta of buzz words. Sadly I could not maintain saintly and do this.

Project Description

Sometimes you search for a package, and you don't find it because you're not typing it right. Of course there's regex support behind the scenes but it requires conscious effort to make use of.

Right now, every time a new team wants a new room in our Jangouts instance, they have to ping me and I have to manually create the room. That means:

Now we are lack of using internal wiki page to solve problem. One of the reason is that we don't know if it contain the solution we need, and it's not convenient to search it manually in wiki page. It's much more slower than using google. In one group, we are most likely facing the same problem during work. So keeping the best solution, which we got from searching engine, in internal wiki is an efficiency way to collect standard workflow.

The current Jangouts UI is limiting us when thinking about adding new features. Some examples:

While normally data is passed to linuxrc (including an AutoYaST profile), modern auto-install tools like Ignition from CoreOS support a very interesting method: the QEMU Firmware Config device.

Description

Continue the work on kqlite (Lightweight remote SQLite with high availability and auto failover).

The situation of maintained ansible roles for boring server stuff like setting up a LEMP stack (Linux, nginx, mariadb, php) is dire and I would like to improve that. This project is about creating a handful of ansible roles with focus on

A frame work for automatically analysis the result of the performance test. The tool can be used manully as well as used throught openAPI.

As DBus a main component in Linux user space, in this hackweek I plan to learn more about it.

https://gitlab.com/JanZerebecki/transparency-log-watcher

libvirt+Xen should support the qdisk (qemu) rbd backend, providing native access to block devices hosted on Ceph clusters. Adding this support to the libvirt+Xen toolstack will also improve interoperability with SUSE Enterprise Storage.

A new Puppet Master will be set up for the openSUSE and public SUSE infrastructure. We will need to move the puppet code from the old server to a new Gitlab instance, deploy it to the new box with r10k, and perform syntax, validation and RSpec testing through ci.opensuse.org

This project is about fixing this known Jangouts issue that is reported over and over, since many user experiencing problem with the outgoing WebRTC traffic or with camera authorization can "lurk" what happens in the room without being noticed.

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