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.

The webVTT standard (nearly the same as the older SRT subtitles) allows to add subtitles to a video. We could use this in openQA to show which keys were pressed at that point in the video, in which line of code we were or on what event we waited. This could make debugging easier and might be instructive to users, too.

I would like to learn Salt by converting ansible scripts to salt states. Current ansible scripts do some QA tasks on cloud nodes, so i thought it would be a good idea to convert them to salt after reading salt tutorial.

Displays your openQA instance status, the feature/behavior should had at least like the list below,

There is a ramdisk block device (brd), and there is a null multiqueue device (nullblk). The one can do I/O, but doesn't use multiqueue, and the other does multiqueue but cannot do I/O.

My home server, and my other box hosting https://sysrich.co.uk are both in need of a bit of a refresh

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.

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