Description

When Uyuni switched over to the containerized proxies we had to abandon salt based saltboot infrastructure we had before.

I wanted to work on something test related this hackweek since we always need more automated testing of our virtualization-related packages. There are many possible test-related topics, but I think a good addition would be more unit tests that are run during build time, e.g. during 'make check'. Additional tests of this nature would then be run by upstream developers and the various distro CI setups, exposing the tests to more environments than would typically be available within SUSE.

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.

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):

The current disk layout recreation code in ReaR is about 10 years old now and more and more

Description

Investigate the state of bioinfo FOSS (mostly interested in DNA sequencing and sequence analysis) on Linux (and possibly other platforms), learn some algorithms, learn to use the available software, find what needs to be improved and if time permits, start improving.

Having worked on KVM for a long time, it's time I actually start using it myself! I now have a high enough powered laptop to have a permanent setup on my laptop to do almost all the testing needed for releases, as well as maintaining playgrounds for upstream work and involvement. This will include nested virtualization, which is getting pretty bulletproof in latest kernels, as well as being able to play more with these other architectures that we now support KVM on, via improved TCG emulation (of course some testing and development will always rely on the physical hardware, but still a lot can be done via TCG incl. user-linux mode. I'm also seeing which aspects of pass-through testing will make the most sense to perform on the laptop (pci, usb, video, filesystem, etc.).

https://github.com/dmulder/phylogen

Description

There is plenty of hacking on osc, where we could spent some fun time. I would like to see a solution for https://github.com/openSUSE/osc/issues/2006 (which is sufficiently non-serious, that it could be part of HackWeek project).

Description

Harvester teams use Harvester seeder in our lab for dev / qa work.

Create a selector of BCI-language containers, python, java, go, etc, to pull and build the proper image

Project Description

More and more customers use our products in mission critical environment. They have a huge need that things run smooth. With Hack Week we have the challenge

Create a user interface useable with a see through head mounted display. The display was created from some Chinese video glasses and has a low resolution (320x240) which requires a optimized user interface that also is useful when using it hands free.

Currently I am using astroberry server for all my astroprojects. I have a spare RPi 4, so will try to install opensuse leap on it and configure it so I could use it for my astro projects.

https://hackweek2024annatrofimenko.framer.website/

terminal has it, git tool has it, so yast-devtools should also provide it for new rake tasks

The goal of this project is to write a proof of concept of a new philosophy for yast2-storage-ng. Instead of just extending the API offered by libstorage-ng, the idea is wrap libstorage-ng so the Ruby code using yast2-storage-ng does not have direct visibility (unless explicitly desired) on the libstorage-ng classes and methods.

https://github.com/MalloZup/go-verdura

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

Let's imagine you are a sales engineer. You want to either:

qemacs is a nice emacs style editor by Fabrice Bellard (qemu's original author).

The primary motivation for crash-setup (created by l3team) is to make kernel crashdumps deployment and crash using as easy as possible. This has been the case for quite some time except the tool was quite l3slave centric. With a great help from tcech the tool is close to be fully usable from other machines and !.de network as well.

Create a USB device that, when configured and connected, exposes one or more Ceph RBD images for use as USB storage, allowing for:

or: Static Analysis of nil Values in Ruby Code used in YaST.

Overview

Hi, We would like to make a new demo showcase similar to our previous LEGO excavators https://www.youtube.com/watch?v=fJdZ3kr2u9o

Description

Hashicorp Packer is an automation tool that allows automatic customized VM image builds - assuming the user has a virtualization tool at their disposal. To make use of Harvester as such a virtualization tool a plugin for Packer needs to be written. With this plugin users could make use of their Harvester cluster to build customized VM images, something they likely want to do if they have a Harvester cluster.

I use Calibre (calibre.com) in my opensuse. This tool manage ebooks, convert for many formats and control a ebook reader device. I would use my time to finish portuguese Translation to this project.

Get some basic understanding of Rust security related features from a general point of view.

Description

Description

There are currently 2 versions of tracking fixes. One is used in CI (and ./scripts/git-fixes)[1] and (unfortunately, it doesn't handle reverts) the other is for sending emails to developers. The first one is relatively fast (for its usecases) and the other is relatively slow and made for bulk processing only. Both are single-threaded.

We had a quick course of Coccinelle during the last Labs conference. The tool is really great and I would like to explore possibility of checking lock invariants for particular functions. Julia was really prompt and implemented something that should help but I didn't get to it since the conference.

From the kernel-source git repository for SUSE kernels we can extract the people who backported a patch and the files a patch touches. Use this information to build a database for which paths are touched by which developers and write a tool to find the most relevant people for a given source path or upstream patch.

The result for xfstests in osd seems always red[1], but actually it's only a few test fail in a group(around 1/50). If we want to keep use openQA to handle those test, we need some enhancement for that. Try to enhancement test result to make it shows in a better way. - Make more reasonable group for those test

Diagnosing issues with stalling desktop application (or a whole desktop environment) is difficult these days as the application often requires multiple processes interconnected with sockets, pipes, futexes, etc. to work and often it is not clear which process is the one responsible for blocking the whole ecosystem. The idea of this project is to write a tool that gathers information about processes in the system and for each process that is sleeping display the resource (file, socket, futex) it is waiting on as well as the process that is likely responsible for unblocking (feeding pipe, sending data to socket, unlock futex, ...). Once the information is gathered, we can also plot it for graphical displaying with tools like graphviz.

Project Description

Just have play with bpftrace on some real kernel bugs.

Description

Migrate integration tests at r/r https://github.com/rancher/rancher/tree/main/tests/v2/integration/steveapi to steve using CoPilot with the new approach created by TomLeb.

If you want to use the full potential of SSDs as primary (and possibly only) storage on SLE or openSUSE systems, you are supposed to perform several configuration settings to make it fly, including:

in https://gohugo.io/ you can easily write custom themes via templates for creation of static websites

Description

Description

This project aims to create a Nextcloud container image built on openSUSE, leveraging the upstream Nextcloud image structure while integrating the unique benefits of the openSUSE Build Service (OBS). The goal is to maintain compatibility with upstream while incorporating openSUSE’s tools, package management, and system utilities to ensure a robust and familiar environment for openSUSE users.

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

Moving objects to a new container is a problem everyone in R&D has faced at least once in his life. It requires a very advanced algorithm to pack the many different objects (which are generally heterogeneous, with different uses, types, weights and sizes), before the packs can then be transferred to the new container, generally through a dedicated bus. We can identify some usual cases:

[MTUI][MTUI] is a tool used by QA-Maintenance in testing maintenance updates. Saddled with a host of questionable choices for its interfaces and implementation, it includes a number of difficult-to-fix bugs and hostility toward change. While not the first choice for me, the time's come to scout out a different approach. Welcome SMRT.