As you may already know, AutoYaST offers integration with Salt and Puppet through the YaST2 Configuration Management module. Some months ago we got a feature request to add support to Ansible, another quite popular automation tool. It should be rather easy to add basic support for it.

Our internal openQA server is running but has serveral limitation. I will update it to SLE12SP3 and try to make it more smart.

The idea is to create a new standalone project on GitHub that provides a minimal (e.g. Python Flask-based) server implementation Formulas with Forms that anyone can embed into their own Salt projects.

This is a documentation-only project: Describe how we did the SaltConf 2017 SUSE keynote demo and check in the code examples as a GitHub project.

Idea

SUSE Manager's Formulas with Forms are a powerful way of allowing admins to parametrize Salt states for groups of systems or individual systems.

In crowbar for each barclamp we can change some attributes using comfortable UI fields, but sometimes we need to change some attributes that aren't defined in these fields therefore we have to manipulate a json in a text area to change them. I propose user-friendly method to set these attributes: Selecting the attribute you want to change and setting the value.

The Machinery project adds one feature to SUSE Manager that even Salt in its current state can not fully provide: You can scan a complete system for all programs, configuration files, users, and services that are present, and compare those over time. The first goal of this hack week project is to create a standalone server (or container) that is going to be the Machinery "collector", and then loosely couple it through Salt, e.g. via a Salt Runner like the Spacewalk Runner or a Salt Proxy.

Supportconfigs are huge blob of text which we are asked to examine and deduce issues from. Sometimes the solution to a problem is quite simple.

Why a Dashboard?

In the YaST team we use quite a lot of external or internal services like GitHub, Travis, Jenkins, Open Build Service, Bugzilla, Trello,... It is too difficult and time consuming to track all those tools and get an overview what is OK, what failed and what actions should we take to resolve the problems.

I want to improve my C skills and pick up some knowledge about Gtk+, Glib, Gobject... Some GNOME C projects might be a good place to start:

tool to split the header and body of an OpenPGP digital envelope

Repository

One of the significant advantages of Wayland is about security, to isolate input/output of every single windows, encourage non-root user running the core process, as well as discouraging root user running any graphical applications. The project wants to have a close look at Wayland trying to address the questions: - how is wayland exactly integrated in current gnome stack of Tumbleweed/SLE (gnome-shell, mutter)

Microsoft Azure offers a bunch of interesting RESTful protocols, providing access to objects (Block Blobs, similar to S3 Objects), disk images (Page Blobs) and file systems (Azure Files). The underlying services seem to map pretty closely to RADOS, RBD and CephFS respectively, so adding support for these protocols to Ceph, despite being a lot of work, should be relatively straightforward. I've already worked on implementing a C client for these protocols via Elasto, so it might be worth reusing the same code in implementing the server functionality atop the public librados / librbd / libcephfs libraries. The other option would be to use civetweb/rgw, which is already embedded within Ceph for S3/SWIFT gateway support.