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.

The bootloader menu has to be able to list snapshots created with tagged attribute by snapper or other tools. These attributes control how snapshots are displayed and organized in the boot menu. All the changes are reflected in real time, that is when a snapshot is created it's ready to boot without the hassle to call grub2-mkconfig to refresh menu. The operation and navigating to the snapshot is intuitive and out of box and booting is even more easy to hit the button.

Project Description

Salt – The most intelligent, powerful and flexible open source software for remote execution, configuration automation, cloud control and event-driven orchestration

While programming is occasionally a very rewarding activity, it's mostly a chore and the rest is filled with frustration. Let's teach an unsuspecting youngster program!

Give a more complete overview of the infrastructure and the processes the documentation team uses to write, maintain, and publish the documentation for the SUSE products. Add missing information/chapters to the guide.

Find where an openQA module is running

The idea is to produce a standalone, independent tool to save and restore windows positions and sizes, analogous to a similar feature in KDE desktop. This would be handy in various lightweight desktop enviroments.

Quite a big part of openQA is testing the installation of SUSE products. All of them are installed by YaST. So a big quantity of problems found during openQA testruns are YaST problems.