This project aims for enabling FCoE over virtio-net. With that we should be able to run FCoE within a KVM guest, and finally have a 'real' FC host in a KVM guest. This should enable 'real' FC testing, like link failure, multipath operations etc.

Description

I would like to make a simple cli tool to communicate with the OpenQA API

In last hackweek, I implemented a RSA private key parser in kernel: https://github.com/SUSE/hackweek/wiki/RSA-private-key-parser-in-kernel

There is a number of possible improvements to the architecture of SUSE Manager / Salt integration that should be investigated in order to improve the reliability and scalability of the backend:

QA uses a dashboard (SUSE internal: http://qa.suse.de/dashboard/ ) to provide an overview of various data to assess the quality of a product.

This would be a multiple step solution, a first idea that I would explore would be:

Currently, each filesystem developer does his fstests runs (a testsuite for regression-testing of filesystems) on his dedicated test machine, on Orthos machine, ... This not only means duplication of efforts to automate this testing but also leads to inefficient use of resources (sometimes the test machine is just idle, sometimes you would need more tests to run in parallel to speed up development). The goal of this effort is to use SUSE Engineering Cloud to implement fire-and-forget fstests runs where you specify kernel to test (fetched from git tree or so), fstests configs to run, and then just pick up test results later on...