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:

This project is about using Salt SSH for managing systems without the need of an additional agent to be installed (besides sshd). With the SSH protocol the connection is initiated by the management server, thus Salt SSH can be used to even manage systems that are located outside of company firewalls, i.e. machines that cannot access a salt-master due to firewall restrictions.

What is Qubes OS

The idea is to create a bootable medium (eg. pendrive) that allows:

Parametrizable formulas is a normal salt module plus some metadata in order to interactively parametrize them. The metadata is used to automatically generate forms that are then injected as pillar data.

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:

See https://github.com/viccuad/salt-configs .

The SLE15 development model follows the Factory First policy, where all submissions need to go first to openSUSE:Factory and then to SLE15 repos. This way more bugs are fixed, less patches get lost, less backporting is happening etc.

There is a couple of libraries available for asynchronous and non-blocking processing of HTTP requests (in Java) that can be used to avoid having threads waiting for responses in request intensive applications, for example:

Salt – The most intelligent, powerful and flexible open source software for remote execution, configuration automation, cloud control and event-driven orchestration

[CaaS] [CAP] Work on a long term solution for L3 team to easily reproduce customer's issues

"salt-toaster" allows you to test multiple Salt package flavors across different operating systems via Docker containers. This project is heavily used on the SUSE Manager team to hardening the Salt package that is shipped on the openSUSE/SLE distributions. Link to GitHub repository

What is Brine?

The salt-toaster (https://github.com/openSUSE/salt-toaster) is a tool created and developed by SUSE employees that we've been using for testing Salt since few years ago.

At SUSE we've implemented a module on Salt called ansiblegate which allows to run and manage your Ansible clusters using Salt.

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):

Salt is moving towards a plugable architecture using POP and Idem. This project is about experimenting with those new concepts by applying them to a real life case: the virt execution and state modules.

Mash is a Python based CI/CD pipeline for automated testing and publishing of public cloud images. Currently the production and development deployment for the package is inconsistent, slow and manual. This is a barrier to rapid development, deployment and testing. It also means the development workflow is different than production. This can lead to production issues which were not seen during development.

There is a number of annoyances and pending improvements when working with the Salt Formula for provisioning Prometheus Exporters in Uyuni:

I'll continue the effort I started at last Hackweek to support Windows clients in Uyuni/SUSE Manager using Salt. When this is done, SUSE Manager would act as a WSUS server to Windows clients.

Language Server Protocol (LSP for friends) is used in a number of code editors these days. There are implementations for various languages, but none for Salt States.

Project Description