There is always something to do if you run the infrastructure for such a big project like openSUSE....

Project Description

This idea has been partially implemented for JeOS images, where we are collecting some data from the images whenever a new build ends up in openQA. For instance, https://openqa.opensuse.org/tests/2419705#step/image_info/9 is collecting the size of the image, as well as total number of RPMs, the list of RPMs with their size and some filesystem information.

In https://github.com/SUSE-Cloud/automation/ we already have mkcloud, which can setup a whole SUSE Cloud on a single host for testing. However, it would be cool, if (instead of a single machine) we could use cloud.suse.de with its capability to add extra networks as requested.

RISC-V is an open ISA (Instruction Set Architecture) based on RISC architecture. It's originated from UC Berkeley and it's attracting more attention in recent years because of its full open architecture so every developer has opportunities to get involved in application processor design or apply it into different applications, such as IoT, Robotics, ... etc.

This is mostly a learning activity for myself, others may benefit from documentation.

Description

I want to improve my personal server hosting environment. The key tasks include exploring OpenMediaVault which i've freshly set up, migrating existing Docker instances to docker-compose.yml files for streamlined deployment on Portainer, revamping the landing page built with Hugo, and investigating the potential of using Homarr to replace the current landing page for a more dynamic user experience. If there's enough time, i want to also improve the backup procedure, which is currently not covering all services.