Once again, the SUSE band is coming together to make music and we're planning a party this time round!!!

New Development

As every hackweek, lets package/update/cleanup some stuff fore factory:

The idea behind the project comes from recent work on integration of OpenDayLight with Suse OpenStack Cloud 6/7. The goal for this Hackweek project is to realize a demonstrable NFV use-case on Suse OpenStack Cloud with as much reduced manual orchestration as possible. The use-case to consider is to run a Service Function Chain(SFC) with basic Network functions like Firewall/QoS that run as services on JeOS Guests on SUSE OpenStack Cloud (SOC).

Orcas are amazing animals. They are playful, intelligent, great swimmers, and very social. They also love to play with their food, hunting down their prey with advanced strategies - understanding where its prey hides, how it will try to escape, and how to overcome those tactics - and having a lot of fun doing so, before relentlessly tearing it apart, killing it, and eat it. Not necessarily in that order. Oh, and they have the right color scheme.

This is the tool I've been working on since HW11 and it needs more work. Actually, there's always something which could be done on it. It is basically an x86 instruction decoder with special emphasis on the kernel and decoding interesting pieces of it in order to help in the development of low-level patching techniques, among others.

Description

It can boot up from udisk/floppy.

Currently, the usual way to communicate with VM instances in the cloud from outside is ssh. This is okay for most uses, but a) does not work when you mess up with the guest's ability to network and b) requires a free floating IP.

PXEAT (stand for PXE Administration Tool) is a tool to easily deploy and manage PXE service.

DAPS is the tool used by the SUSE documentation team to generate HTML, ePUB, PDF, ... output of the SUSE manuals from DocBook XML sources. It uses the suse-xsl-stylesheets for this purpose.

openvswitch is used by cloud infrastructure (e.g. OpenStack) and software defined networking stacks, often in conjunction with KVM and Xen compute resources. When creating workloads on KVM compute resources, orchestration services can specify the openvswitch interfaceid and port-profile of the workload's virtual interface(s). E.g. orchestration can create workload configuration containing

Geeko's Hack Week Gazette - Nürnberg Edition

Read in a crash or oops-style backtrace and access DWARF information to output the current content of the stack and registers in term of symbols, and the the crash commands to dump/pretty print them. In other words, when looking at a crash dump, answer the questions "Which variable is currently stored in $rax? What is the structure of the stack? Which variable is stored at $rsp+16?"

Make a final attempt to implement a graphical user interface for grub2 (gfxboot2).

While in the past MIPS boards were either low-end PIC32 or found in routers running OpenWRT at most, Imagination themselves have recently released the Creator CI20 board (Ingenic, MIPS32) running Debian. And the Shield Pro (previously iGuardian) kickstarter project (Octeon-III, MIPS64) promises to become a playground for testing KVM hardware virtualization.

This is about porting the old KDE 3 based KDirstat to the latest Qt 5. KDirStat didn't use that much KDE infrastructure to begin with, and KDE seems to be more and more a moving target.

Linux Certification Preparation

Distributed teams, cultural differences, expectations and habits are a natural enemy of vibrant, productive meetings (yes, meetings can be productive!). In this project I'd like to work on a different format and targeted exercises to provide ideas and a resource library to anyone interested in spicing up stale meetings.

The idea is about an easy way to allow users to make upgrades (e.g.: changing from one major version like 15.0 to version 15.1) using a GUI and as easy as they can in Ubuntu.

Last time I checked QEMU lacked support for >= z10 processors. Thus one cannot run SLE12 and newer in a virtual machine on non-s390x host. I'd like to improve the situation during Hackweeks.

To make OpenQA work with real ARM devices, we need to control

As DBus a main component in Linux user space, in this hackweek I plan to learn more about it.

YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table

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.

Right now, every time a new team wants a new room in our Jangouts instance, they have to ping me and I have to manually create the room. That means:

The current Jangouts UI is limiting us when thinking about adding new features. Some examples:

Our previous efforts to enable gdb to open kdumps was not received in upstream as well as we hoped for. The perhaps-acceptable way would be to extend gdb with the possibility of implementing targets in Python, then create example binding to libkdumpfile (which already got a Python binding). We've already tried that, yet it has to be tidyed up.

Clair is a static vulnerability analyzer for containers. Currently it supports containers based on Debian, Ubuntu and RedHat.

Flatpak (previously known as xdg-app) is a bundle system, based on ostree, to easily make available applications bundle to users. Currently, flatpack is available on openSUSE Tumbleweed but we don't ship any runtime based on openSUSE (freedesktop or GNOME runtime).

I've attempted this several times already and each attempt had different shortcomings. I'm kind of curious about how exactly will I fail this time.

Tigervnc comes with two very similar VNC viewers - one written in C++ and one in java. The java one can be embedded in a webpage as a java applet. We use that in our default VNC setup (the one enabled in YaST). That way if user doesn't have VNC viewer installed, browser is enough.

To make sure openSUSE can coexist nicely with an existing Windows installation, we need to have automated regression testing. UEFI and secure boot are especially interesting.That means installing Windows and openSUSE in parallel in openQA.

Automation tools are our emotional friends. Know each other deeper and improve it, it's a way to be harmonious for our friendship.

• Build zookeeper, mesos-master and mesos-slave on SLE12
• Setup a 3-nodes high-availability cluster (zookepper + mesos-master + mesos-slave run on each node)

L3 bug reproduction often requires becoming the admin for a moment. I'd like to write down some nifty tricks I used to get certain “interesting” system configurations to work.

In Beijing HA server room, we have a Huawei switch with a 10GB bandwith uplink FC port, a iSCSI HBA, a desktop computer, and some SFPs, I will build a 10GB bandwith iscsi server.

Implement a Little man computer in the Go programming language.

Try to use Jenkins 2.0 CI environments to trigger jobs which running in openQA

I want to make ruby-lint usable.

Create a console application for a crossword puzzle generator that can be fed with a custom list of word+explanation pairs. It may be used by people to quickly familiarize with a specific topic (e.g. a knowledge area, new hires to the company ...) to at least understand the terminology and the abbreviations that are used. Or to just have some distraction and fun :-)

QA wants to set up a new QA Portal to get an new organized entry point for all Information that is QA related. The Hackweek Project is to start a discussion with the different QA groups, SLE QA, CSS QA and QAM to collect ideas and make a concrete plan.

There is a super cool framework for mobile phone apps available: ionic (http://ionicframework.com/)

Together with my son, I'm working on improving the Salt support in Manager 3.