michalnowak

There were several attempts to integrate ABRT to openSUSE. In this Hack Week I'd like to: 1. review those attempts;

MALLOC_CHECK_ and MALLOC_PERTURB_ variables are environmental variables which help identify problems with Glibc's malloc() allocations. I intend to set them "globally" for every process via /etc/environment file and see, if test suites behave in usual way, identify problems.

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. As VirtualBox has decent command line interface (especially VBoxManage command) it shouldn't be that hard to support VirtualBox in openQA's os-autoinst via svirt backend.

In os-autoinst and installation/bootloader_svirt.pm we currently we support only one-disk scenarios like SLES installation to disk and deployment from a disk in JeOS & CaaSP scenarios. To support RAID tests we need support of adding multiple disks to VMs. Targeting Xen and Hyper-V.

Try various container operating systems & kubernetes distributions and compare them to SUSE MicroOS and CaaSP, respectively.

I'll have a look at Hyper-V 2019 test build and how SLES guest plays with it.

Deploy openSUSE Leap 15.0 image to Linux subsystem on Windows Server 2019 and try things around.

Docker for Windows 18.03 CE supports Linux containers on Windows Server. Let's try that.

SmartOS is converged container and virtual machine hypervisor based on illumos, an OpenSolaris fork. SmartOS supports KVM & bhyve hypervisors and illumos, LX, & Docker zones ("containers"). There are LX-branded openSUSE & SLES images unofficial. LX-brand is implementation of Linux API on SmartOS (similar to Microsoft's Windows subsystem for Linux).

Let's see how correctly the FreeBSD emulation layer works.

Learn Rust by following The Rust Programming Language book.