Share with friends and colleagues on social media

The SUSE Manager team has been churning out one SUSE Manager 3.2 beta release after the other. So I’ve had a hard time catching up with the blog posts. That’s why today you’re getting two blogs for the price of one:

The announcement: Beta 3 is out (drums rolling)!

Beta 3, our final beta, comes with the latest Salt 2018.3.0 that I mentioned in my last post. It’s also based on the latest upstream Spacewalk 2.8 that is only a couple of days old.

If you’ve been participating in the SUSE Linux Enterprise 15 beta program, you can finally use SUSE Manager 3.2 Beta3 to patch your SUSE Linux Enterprise Server 15 systems. Of course, support for SLE 15 will also be backported to SUSE Manager 3.1 and released as a maintenance update.

Here’s a screenshot of the improved UI for syncing repositories:

SUSE Manager 3.2 product filters

SUSE Manager 3.2 product filters

Filter by hardware architectures and name to quickly find the products you want to sync.

You may have heard about SUSE Linux Enterprise 15 being more modular. To make it really easy to work with those modules, SUSE Manager can now automatically select all recommended modules that belong to a product of the SLE 15 family for syncing with one click:

Handling recommended child repositories

Handling recommended child repositories

The team has put a lot of work into making sure that salt-ssh, Salt’s “agent-less” option, works across all supported client operating systems, including those that won’t get an update to Salt 2018.3.0 because their Python version is too old.

Finally, we’ve put the last hands on Salt-based “action chains”. Among other things, Salt can now be used with an action chain to properly patch Salt itself on the client (“minion”) and re-start the minion process.

Looking back: What was new in Beta2?

Of course, with Beta3 you’re also getting all the features that were added earlier with Beta2. I’ve already mentioned “action chains”. They allow you to execute several actions in a row, even things that would be hard to do with a configuration state because it doesn’t survive through a re-boot of the system. A common use case is to

  • stop a service
  • patch the RPM package for that service
  • re-boot the system if needed
  • start the service again

 

There will be more!

If everything goes according to plan, we’ll also see the first release candidate for Manager 3.2 by end of May! It will bring the two remaining features that we still have on our agenda:

 

This is Joachim Werner blogging live from the SUSE office in Nuremberg where the Sun has already set and the weekend will start for me in a few minutes from now. 🙂

 


Share with friends and colleagues on social media
Tags: ,
Category: Announcements, Configuration Management, Expert Views, SUSE Manager
This entry was posted Friday, 4 May, 2018 at 8:23 pm
You can follow any responses to this entry via RSS.

Leave a Reply

Your email address will not be published. Required fields are marked *

No comments yet