Recently I became a (not very proud) owner of Acer Aspire Switch 10E, a small notebook/tablet convertible based on Intel baytrail platform. Replacing preinstalled (32-bit!) Windows 8.1 with (64-bit) openSUSE proved more challenging than expected, mostly because the device is haunted by a 32-bit UEFI so that it took me a week to make it boot without an external USB flash disk.

In ubuntu, you can install grub-ipxe, which adds an ipxe entry to the grub menu. This allows you to easily pxe boot on machines that may not natively support it. You can also use it along with grub2-reboot to remotely re-image a machine. The project has been started here: https://build.opensuse.org/project/show/home:blarson:grub-ipxe

Being part of SUSE's Storage Team I frequently talk about our Deployment tool called Deepsea.

Once more mailprocessing has developed some bitrot, namely this recent crash:

Hydrogen is a software drum machine and pattern editor.

Last hackweek I have use multi-machine for RMT testing. This hackweek I would like to research how to develop the multi-machine at openQA.

Since a few months it is now possible to build an upstream QEMU which includes only our supported VCPU accelerator.

I'm using soundkonverter a lot (my whole music collection is flac, but for the car or my children I prefer mp3) and it is working fine. However when doing mass conversions, building the list of files to convert can take ages. It seems the filelist is being re-created for every title added. Debug it and try to fix it in order to speed up this operation.

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

We had old arndale images working, but those were based on openSUSE-12.x which is now long obsolete and bad (e.g. missing security updates).

The openSUSE build service could build hundreds of packages in parallel but in practice serial package dependencies prevent that.

I wanted to work on something test related this hackweek since we always need more automated testing of our virtualization-related packages. There are many possible test-related topics, but I think a good addition would be more unit tests that are run during build time, e.g. during 'make check'. Additional tests of this nature would then be run by upstream developers and the various distro CI setups, exposing the tests to more environments than would typically be available within SUSE.

Since there is no real documentation about openQA's lib/ functions I wanted to kill two birds with one stone and write a parser in perl that extracts all function names (and maybe preceding comments) in said directory and improve my perl knowledge by doing this.

An initial prototype from the last hackweek can be found on YouTube

I just got the FST-01G device from my friend, which could work as the Gnuk token. I'm going to try to make it work for ssh authentication.

Currently, way we distribute ssh keys within QAM on our testing infrustructure is a bit cumbersome - maybe we should try to (ab)use existing salt used by our internal infra team.

My goal is build on Alberto's work on "yomi" and the new Salt-based virtualization management features that Cedric has contributed, then combine them with a Redfish prototype to do the following from one (ideally idempotent) Salt state (orchestration state if required):

The idea is to hack os-autoinst-distri-opensuse infrastucture and explore design patterns that can fit. The end point of this is to restructure the framework in such a way that the main-common.pm is more efficient, functional and readable.

Description

• jruby
• ruboto homepage

Project Description

The Robot Operating System (ROS) is a set of software libraries and tools for building robot applications. From drivers and state-of-the-art algorithms to powerful developer tools, ROS has the open source tools you need for your next robotics project.

Description

Our scalability and performance testing swiss-army knife tool Dartboard is a major WIP so why not add more scope creep?

The goal of openQA is "test as a QA engineer". But openQA has no ears - all we can test for are DTMF sounds. And even those are very bad.

Goal:

I'd like to learn Docker and Kubernetes. I'd also like to learn about AWS so I'll use that platform using the free tier account.

Metal³ is the idea to support a declarative bare metal cluster management for Kubernates by employing a simplified stand alone version of Ironic.

The current disk layout recreation code in ReaR is about 10 years old now and more and more

Examining vmcore with crash (very) often means to look at multiple outputs at once, which in console enviroment simply is not easily achievable. Since last hackweek, there is a

Project Description

Investigate the state of bioinfo FOSS (mostly interested in DNA sequencing and sequence analysis) on Linux (and possibly other platforms), learn some algorithms, learn to use the available software, find what needs to be improved and if time permits, start improving.

While packaging node.js modules, which often depend on specific versions of other node.js modules, sometimes many of them, you easily end up in dependency hell, and maintaining an OBS project with a few hundred of those modules can be a tedious task.

Hallo Welt!, the company behind Blue Spice Media Wiki (an open source, subscription based enterprise wiki) is interested in howto package their PHP software, get it into OBS and into the whole workflow with openQA and learn how to write automated tests. This is such a generic task that I though documenting it might be worth an afternoon at hackweek together with Richard (openQA) and Darix (OBS and packaging). I'll reserve a meeting room, doc team will provide the documentation of this workflow in a "SUSE best practice guide"

Having worked on KVM for a long time, it's time I actually start using it myself! I now have a high enough powered laptop to have a permanent setup on my laptop to do almost all the testing needed for releases, as well as maintaining playgrounds for upstream work and involvement. This will include nested virtualization, which is getting pretty bulletproof in latest kernels, as well as being able to play more with these other architectures that we now support KVM on, via improved TCG emulation (of course some testing and development will always rely on the physical hardware, but still a lot can be done via TCG incl. user-linux mode. I'm also seeing which aspects of pass-through testing will make the most sense to perform on the laptop (pci, usb, video, filesystem, etc.).

Aims to understand Flatpak(previously aka xdg-app), an application sandboxing and distribution framework (formerly xdg-app) on Linux. The final goal is "build my first app".

Currently, As QA, we design matrix for the test cases, then use matrix to generate test cases' name, then according the test cases' name to add related settings, then add those cases' name and settings to the openQA test suite. I hope, we can design matrix first, then other steps will be generated by automatically.

https://github.com/dmulder/phylogen