this work has experimented with zeromq sqlalchamy and multithreading in python to make a rich tool for syncronisation of your music collection with media devices. This project will attempt to pull all this research into a product.

For Hibernate Signature Verification - HMAC version, I need a hash algorithm in EFI stub environment before ExitBootServices() to mix / mess random seed from different sources (rdtsc, rdrand...) for generating the HMAC key to sign the hibernate image in runtime environment. There have no any hash functions provides by EFI services, so need implement it in EFI stub. I choice SHA1 to be the target algorithm because currently I choice HMAC-SHA1 to be the algorithm to generate signature of hibernate image.

I had presented the "Wicked Network Manager" talk at openSUSE Asia summit @Beijing. I would like to keep studying the topic continuously. Getting involve the source code and study the operating style and components. I also met some problem after discussing and testing issues while my research , I want to keep it as a record and writing the technical document on wiki too.

Tool to inspect the meta data from a mini DV firewire transfer and report any quality problems such as dropouts. Preferably a gstreamer 1.x based tool.

Report from the research mailing list: some colleagues and myself had a small SLES 12 troubleshooting workshop today. We were playing around with the rescue system. There is this magic tool called "systemd-nspawn" that is

Current kGraft implementation allows to apply new patch only when the previous one is applied to the whole system. Every task is handled separately and it needs to wait for a safe place to switch. It might take a while, especially when the task is sleeping. Therefore it would be great to allow to apply more patches in parallel. It is not trivial because different tasks might be in different world, so the slow stub has to be clever and choose the right one without taking any lock...

Firefox dropped its built-in ntlm auth as it only handled ntlmv1 (insecure). On windows it uses SSPI to handle the ntlm cases, and on other platforms it simply does not support NTLM at all (and then only v1) without a manual flag change. Let's get it recognizing /usr/bin/ntlm_auth as the system tool for doing this.

Reverse engineering partially done already. Help appreciated with - decoding video stream from camera (overlay?)

The Allwinner Tech Optimus Board by Merrii is the evaluation board for the Allwinner A80 SoC with big.LITTLE Cortex-A15/-A7 configuration (32-bit ARMv7). The sources leaked from Allwinner contain GPL violations in U-Boot and Linux kernel and therefore won't easily build with openSUSE's armhf gcc (binaries seem to be softfp).

The Nvidia Jetson TK1 is an SBC with Nvidia Tegra K1 SoC (quad-core Cortex-A15, 32-bit ARMv7). I have openSUSE running on the Jetson TK1, but KVM is currently not usable as the CPUs are not booted in HYP mode. Thierry Reding of Nvidia has some work-in-progress for U-Boot and upstream kernel that I would like to test.

The Inforce Computing IFC6540 is an SBC with Qualcomm Snapdragon 805 SoC (32-bit ARMv7). I had previously brought up openSUSE on the IFC6410. A week before Hackweek Interstellar I got the IFC6540 to boot on serial console using the upstream-based Linaro integration branch, up to searching for the rootfs. Since USB and SATA support were still missing, my goal will be to prepare a MicroSD based rootfs to complete the bringup.

The Firefly-RK3288 is the first SBC with the Rockchip RK3288 SoC, the first available chip with Cortex-A17 cores (32-bit ARMv7). I received such a board just in time for Hackweek Interstellar and will be looking into booting an upstream kernel with openSUSE 13.2/Factory rootfs.

The open-iscsi package is the de facto standard Linux iSCSI initiator, but it does not support iSCSI MCS. MCS stands for multiple connections per session, and it means that the iSCSI initiator and target communicate over multiple connections to increase throughput. It is sometimes written as "MC/S".

Create a single node installation of OpenStack with the OpenSUSE OpenStack Quickstart scripts for 64 bit ARM (aarch64).

Learn the grub2 network stack and have fun with ipv6 network booting. :D

With many Proof of Concepts (PoCs) going on for SUSE Cloud, the development team has observed that we have no clear path on how Sales Engineers (SEs) and sometimes dedicated support engineers (xSE) can receive technical support to successfully complete the projects, often leading to escalation calls and even firefighting on-site visits by developers. Goal of that project is to come up with a best practice guide and to eventually set expectations on what's possible from a development point of view. Results should be documented in a central internal location and announced to all relevant parties.

Retty is a tool for changing stdin,stdout,stderr of a running process (http://pasky.or.cz/dev/retty/) which may be handy if you want to attach to a process running e.g. from a died ssh session, changing running process to run from under screen(1) etc.. Currently it doesn't work for 64-bit systems and it doesn't handle changing of a controlling tty of a process (which may be possible using setsid() and opening a new tty). The aim of this project it to fix the above deficiencies and package the tool in OBS.

Play with Docker orchestration tools like the ones provided by CoreOS, OpenShift and kubernetes. Provide packages for openSUSE and SLE.

see iqlight.com to understand what an IQ Lamp is.

Create a system to allow a community to add contextual information to "open books". Think wikipedia for books

Predicting the non-functional properties of a Ceph cluster can be quite difficult. There are many inputs in the hardware setup and software configuration that affect the resulting availability, reliability and performance (latency and throughput at nominal levels and during degraded and rebuild times). I want to understand the interrelationship of these parameters better and build a (perhaps interactive) model that allows us to predict the result without the need to build a ten thousand node cluster.

provide a summary report of data from a sar data file. Report should be broken down into subsystems - cpu, memory, disk, and network, and provide individual summaries for each device (cpu, disk, nic).

I want to revive my "Cloud in a Box" project and this time focus on how OpenStack's Heat automation framework can help with setting up a complete demo or QA environment consisting of several SUSE products (e.g. a SLEPOS Admin/Branch/Client environment). Looking for contributors who want to hack OpenStack (especially work on a Horizon UI plugin for managing Heat-based "SUSE blueprints").

Although I've been maintaining CRIU package, I had little time to play with it recently. It's still interesting especially in combination with various containers. So let's spend (or waste) some time.

I'm sitting on old patches that implemented predicated value numbering in GCC by combining the algorithms from http://portal.acm.org/citation.cfm?id=512529.512536

There is quite a popular Android software for connection OBD standard adapters but not for older, brand specific ones. One for pre 2001 VAG cars is this one:

The kdump package can now use SMP and multiple targets with constant memory requirements. The goal of this project is to find the optimum parameters for dumping a very large machine (SAP can give me access to 6TB, SGI is able to test with 64 TB).

The idea is to produce a standalone, independent tool to save and restore windows positions and sizes, analogous to a similar feature in KDE desktop. This would be handy in various lightweight desktop enviroments.

If you want to use the full potential of SSDs as primary (and possibly only) storage on SLE or openSUSE systems, you are supposed to perform several configuration settings to make it fly, including: - changing the io scheduler of the device to noop or deadline

We had a quick course of Coccinelle during the last Labs conference. The tool is really great and I would like to explore possibility of checking lock invariants for particular functions. Julia was really prompt and implemented something that should help but I didn't get to it since the conference.

Starting with CUPS 1.6 things have changed considerably. Clients are no longer discovering broadcasted printers anymore. Distributions (e.g. Debian) has backported the original protocol into cups-daemon package but this doesn't seem to work either on my laptop. I would like to look and try to understand what the hack is going on here. The outcome should be my understanding of the change and how to configure CUPs to behave reasonably again.

cscope is a great tool index C/C++ sources and allow to navigate through the code. I have learned that the project is mostly dead and what is worse it uses its own database format to store the index. I would like to see some extended functionality in the tool - e.g. search whether a function A is reachable from B, filtering search results per-file, fix functions with function parameter detection (such functions are not recognized properly currently) and some others. See if the cscope specific storage can be replaced by a more generic database (sqlite?) and understand how the code flow works so that new extensions would be easier to implement.

The primary motivation for crash-setup (created by l3team) is to make kernel crashdumps deployment and crash using as easy as possible. This has been the case for quite some time except the tool was quite l3slave centric. With a great help from tcech the tool is close to be fully usable from other machines and !.de network as well. Let's finish the last pieces. This looks like a very minor project but it will be great to have it finally!

The CRUSH algorithm determines how to store and retrieve data by computing data storage locations. CRUSH empowers Ceph clients to communicate with OSDs directly rather than through a centralized server or broker. With an algorithmically determined method of storing and retrieving data, Ceph avoids a single point of failure, a performance bottleneck, and a physical limit to its scalability. CRUSH requires a map of your cluster, and uses the CRUSH map to pseudo-randomly store and retrieve data in OSDs with a uniform distribution of data across the cluster. This project aims at creating graphs of the crush map, for better visualization of the Ceph cluster.