Mojolicious is a web development toolkit and framework built around an event loop. That has many performance and scalability advantages, but can also make debugging slow code a bit of a challenge.

For far too long openQA instances are crippled by insufficient I/O throughput when under heavy load. This results in incomplete and aborted tests prolonging new snapshots testing and also adding confusion into the release process.

Fedora 25 has enabled Wayland by default for GNOME.

In the spirit of learning more python and practicing I will be creating a script to automate the work report emails that we send every week. This will not be a simple cron job because I have to catch corner cases of vacation etc. The next step is filling the workreport automatically by using the various API's that we can use (Bugzilla, osc qam plugin). The purpose is mainly to learn a bit more python.

You know Tetris, right? You know Telegram, don't you?

Control you openQA instance from an Amazon Echo!

In openQA we support various backends which are able to 'host' tests. 'svirt' - one of those backends - is so generic that it allows to conned to a virtualization host via SSH a perform shell commands directly.

By default, let's encrypt allows to get domain for server where you resolve an HTTP challenge. This is sometime not possible to setup (because the server you want your SSL certificate isn't running a HTTP server).

The Mojolicious web development toolkit is currently limited to using TCP/IP sockets for its HTTP/WebSocket client and server. For most web services that's more than enough, but for containerized applications and IPC, UNIX domain sockets could provide significantly better performance and security.

CVRF is a standard where security advisories are encoded in a XML format.