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.

With 'pint' the Public Cloud Team already provides a command line based tool to get information about the images we're hosting in the public clouds. It's provided via the Public Cloud Module in SLE as well as in the Cloud:Tools repo.

Simplify the codebase by using a more modern toolkit to accelerate maintenance and future development.

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.

It would be nice to have a OS that can be tinkered with easily by having only a compiler as the only binary on the system.

The next release of Ceph (Octopus) will be delivered via containers.

The goal is to use the work from the debug-early GCC branch to generate better debug information for LTO compiled objects, especially with regarding to language specifics like classes and templates. This has now been achieved and openSUSE Factory

I have several themes in progress, they all need lots of work before they could be used with openSUSE. * The gtk people keep changing things so the gtk theme I use to match my enlightenment theme also needs fixing.

openSUSE Leap 42.3 goes for a rolling release model with automated openQA tests. That covers only so much though. We need manual testing too. In previous releases a google document spread sheet was used to coordinate and track the efforts.That's probably not the best method anymore.