In SUSE Manager we want to offer support for bootstrapping systems that don't have the salt-minion installed and configured yet. This can be done using salt-ssh given just a hostname, username and password. See the docs about salt rosters for even more options. What we are missing:
- Support for using salt-ssh in our library
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.
Porting openSUSE to MIPS will involve setting up an OBS instance linked to Factory (update: done) and cross-compiling a set of packages for an initial bootstrap (update: in progress). Maybe this can be scripted to some degree, as there will be some overlap with the ARM ILP32 port project.
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.
See original Hackweek project, SUSE Manager support for formulas blog article and its (internal for now) docs.
RabbitMQ is, in this hacker's opinion, hard to run, hard to scale, hard to debug, and difficult to run in a HA situation. ZeroMQ takes a different approach from the centralized broker model, and instead runs a daemon on every machine that needs to send or receive message over the bus, and communicates directly between machines.
* Package up zeromq.
sumaform is a set of terraform modules to deploy SUSE Manager installations originated in Hackweek 14.
One year later, it is used virtually by all SUSE Manager developers daily and in our automated test suites - some consultants and SEs also use it.
For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project.
My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:
Packages added by the dependency solver in order to resolve a user's request, are marked as having been automatically installed. They may later be removed, if no more manually installed packages depend on them (e.g. by zypper remove --clean-deps).
However things may go haywire. Automatically installed packages may turn out to be useful, and you may want to exclude them from any automatic cleanup. And vice versa.
1% of SUSE Manager's functionality in 0.1% of the lines of code
Let's create a much simpler SUSE Manager — one you could use at home! Users should be able to deploy and operate in minutes with minimal configuration, while still retaining the very core features that make SUSE Manager useful!
SUSE is well known for the standard enterprise linux distribution (aka SLES). As a result, most of the customers we have are not cloud-native, so cool stuff like microservices and serverless are no gonna happen within the day for them. There is a very good chance that some old monoliths running in Cobol today, will continue running in the same way for the next 10 years. However, companies are evolving and some parts of the business might (or they can be already) converted into containers. So what happens now? They have to keep maintaining two infrastructures:
* a modern kubernetes infrastructure
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.
This tool uses pytest in combination with Docker containers to allow testing the multiple versions of the Salt codebase and as well as Salt packages across multiple distributions.
At SUSE we've implemented a module on Salt called ansiblegate which allows to run and manage your Ansible clusters using Salt.
This a very powerful module that bring lot of value to Salt when the users are planning on migrating or starting to use Salt and they already have an existing Ansible infrastructure.
The experience while navigating throughout the UI of Suse Manager it's not that nice. Whenever we navigate to a new page, the whole page gets refreshed and recreated, even when half of it didn't change a thing, for instance, the menu, topbar, and the notifications WebSocket connection, which in my opinion doesn't provide a smooth experience.
This project has the goal to test out an automatic way to transform the Suse Manager UI into a Single Page Application.
The goal of this project is to create video tutorial describing configuration of SUSE Manager for Retail.
There is a precise documentation describing every step of its configuration, but SUSE Manager for Retail is still a very complex piece of software and there is a lot of things to be configured configured properly (proxy configuration, Kiwi image building, DNS, DHCP, etc.) in specific order to get it finally working.
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):
* mount the installation media via Redfish