After blogging about SUSE Manager 3.2 Beta 1 last week, this afternoon I was planning to look into what’s going on in our stable release, Manager 3.1. And I suddenly realized that we’re currently at version 3.1.4, the perfect release number for a blog on this week’s “Pi Day“.
Well, a missed opportunity for me, but that won’t stop me from telling you more about two exciting new features in 3.1.4:
New Notification UI
Let’s start with a new feature that improves the way SUSE Manager communicates with you. And no, we didn’t add a random creepy laugh. 🙂
We now have a new UI component in the header bar to display notifications, especially about events that otherwise may get lost in some log file. The new bell icon indicates how many new messages you have. And you can read and manage them on the new page “Home > Notification Messages“.
Initially, this will show three type of messages:
- Salt bootstrap failures
- Channel reposync successes
- Channel reposync failures
Each message can be flagged as read or unread or deleted completely. For each failure a customized button (in line with the message) is available to react to that failure.
The type of messages will be extended to cover more information in later releases.
Configuration Management UI for Salt
This is a feature that started as a tech preview in Manager 3.1.3 and is now fully supported. It’s actually two features for the price of one:
- If you’ve been using the traditional configuration file management feature with its configuration channels and have been struggling with how things are different now with Salt, there is good news for you: The most commonly used part of the configuration channels feature, centrally managed configuration channels, is back for systems that are Salt Minions. And to use it you don’t need to learn anything about Salt at all!
- We’ve also merged the former Salt Custom States UI into the Configuration Channels. This comes with two benefits:
- To start with, you don’t need to switch back and forth between the Configuration Channel UI for traditional clients and the Salt State Catalog feature. Salt States are now just a special flavor of configuration channels. And yes, of course we automatically migrate/import all your existing custom states to the new implementation!
- The new implementation allows you to not just add a single Salt state file, which always was a bit limiting compared to what you can do with Salt on the command line, but you can add file resources as well, and split your Salt states into separate files that you import from the init.sls, just like you’d do it from the file system.
Of course the documentation has been updated to reflect this as well!
The plans we have for the future of this feature include
- making it easy to import or export states from and to the file system, for example if you want to switch from managing your states via the Manager UI to using a GIT-based workflow or vice versa, and
- combining it with the Formulas with Forms feature, so that it basically becomes and end-to-end Salt Formula UI.
This is Joachim Werner blogging live from the SUSE headquarters in Nuremberg, where magic is made into features. 🙂