Share with friends and colleagues on social media

We are thrilled to announce the start of SUSE Manager 4.1 Public Beta Program.
As usual, we have prepared tons of updates and we hope you will like it.
We have a new Public Mailing List, so you can share your feedback with our Public Beta Community, our Engineering and our Product Managers.

Requirements and Beta Registration Codes

SLES 15 SP2 Public Beta is required as base OS, you can retreive it from here.
You will need at least 8 GB of main memory and 100GB of disk space to install the Server and 4 GB of main memory and 100GB of disk space to install the Proxy.

Registration is not working with your regular SUSE Manager key, special Beta Registration Code is required!
You need to request one via email to beta-programs@lists.suse.com.

You only need SUSE Manager 4.1 Beta registration codes for the purpose of installing the SUSE Manager 4.0 Server, Proxy and Retail. No SUSE Linux Enterprise Server registration code is needed.

Notable Changes

Base system upgrade

SUSE Manager 4.1 Beta is based on SLES 15 SP2 Beta! For more details on SLES 15 SP2 Beta, please visit the dedicated sle-beta Web page.

New products enabled

  • SUSE Linux Enterprise Real Time 12 SP5
  • MicroFocus Open Enterprise Server 2018 SP2 (product GA in Q2 2020)
  • CentOS 6, 7 and 8

Recurring highstate scheduling

You can now schedule automated recurring highstate actions for Salt clients, i.e to individual clients, to all clients in a system group, or to an entire organization. The Recurring Actions section in the Administration Guide contains all the details for this feature.

Content Lifecycle Filters for AppStreams

RHEL, SLES ES, CentOS and OEL 8 appstreams can now be mixed and converted to flat repositories using a new type of CLM filter.

Single Page Application UI (SPA)

In an effort to provide our web UI users with a smoother navigation, we have implemented large parts of the user interface as a single page application. This enhancement was started in SUSE Manager 4.0 as an opt-in feature and now becomes the default in SUSE Manager 4.1.

Single Sign-On (SSO)

SUSE Manager supports Single Sign-On authentication by implementing the Security Assertion Markup Language (SAML) 2 protocol. This feature, introduced in 4.0 as a Technology Preview, is now declared stable and fully supported.

Others

There is too much for the announcement, so let’s just mention a few other interesting features:

Please check out our Release Notes for the complete list of changes.

Technology Preview

Yomi (Technology Preview)

Yomi (yet one more installer) is a Salt-based installer for SUSE and openSUSE operating systems. In SUSE Manager, Yomi can be used as part of provisioning new clients, as an alternative to AutoYaST. Yomi consists of two components:

  • The Yomi formula, which contains the Salt states and modules required to perform the installation.
  • The operating system image, which includes the pre-configured salt-minion service.

Detailed information on how to use Yomi is available from the Salt Guide. Yomi is work in progress and more operating systems and features will be added in coming releases.

SUSE Manager Hub XML-RPC API (Technology Preview)

Multiple SUSE Manager Servers can be managed from a single Hub node. The Hub is a Salt master itself and the managed SUSE Manager Server servers are both a minion (to the hub) and a master (to their own minions). More details in our Release Notes.

More Information

As always, there is a lot more changes that we did not cover her. So please visit https://www.suse.com/betaprogram/manager-beta for more information like beta schedule, how to report issues, how to start a discussion with SUSE Manager Beta community and more.

 

Have fun beta testing!

Your SUSE Manager Team

Share with friends and colleagues on social media
(Visited 1 times, 1 visits today)
Tags: , , ,
Category: Announcements, Expert Views, Free Tools, IT Infrastructure Management, News, Promotions, SUSE Manager, SUSE News
This entry was posted Wednesday, 25 March, 2020 at 9:23 am
You can follow any responses to this entry via RSS.

Comments

  • Franz Pförtsch says:

    Hey, thanks a lot for the information. This are great news.

    but what is going on with the ubuntu flavour? I am waiting on support of ubuntu 20.04 LTS and the feature to autoinstall ubuntu from the scratch.

    Today I am installing the apt-cacher-ng on top of the suse manager server and use netboot-mini.iso to install behind a proxy/firewall.

    I am also waiting on automated upgrade from sles12 to sles15 using salt. Today it is only supported for traditional clients.

    best regards and stay healthy

    Franz

  • pagarcia pagarcia says:

    Hi Franz

    > but what is going on with the ubuntu flavour? I am waiting on support of ubuntu 20.04 LTS

    Ubuntu 20.04 LTS will be supported.

    The only reason SUSE Manager does not support Ubuntu 20.04 LTS yet is Ubuntu 20.04 LTS has not been released yet (expected release date is 23.04.2020).

    > and the feature to autoinstall ubuntu from the scratch.

    If you mean preseed, this is something we have in mind but we are not there yet.

    It may be the case we support Ubuntu autoinstallation first via Yomi (try it! it’s available -for SUSE operating systems- in the 4.1 beta we just released!).

    > Today I am installing the apt-cacher-ng on top of the suse manager server and use netboot-mini.iso to install behind a proxy/firewall.

    Why do you need apt-cacher-ng? SUSE Manager (reposync) can sync .deb repositories. Or maybe I am missing something?

    > I am also waiting on automated upgrade from sles12 to sles15 using salt. Today it is only supported for traditional clients.

    It is possible with Salt since SUSE Manager 4.0.5, release 2 weeks ago:

    https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4.0/#_salt_clients_provisioning_api

  • pagarcia pagarcia says:

    Also, remember we have the manager-beta mailing list, that’s probably the best place to continue the discussion:

    http://lists.suse.com/mailman/listinfo/manager-beta

  • Franz Pförtsch says:

    Thank a lot for the quick response!
    I am very happy to hear the status about ubuntu.

    yes, I want to preseed something. I have done something like this (store the preseed file as kickstarter), but the cobbler-part is not prepared to handle ubuntu/debian style. So I filled in SLES stuff as fake 🙁

    I will try Yomi, but this is very new to me. And may be some more additonal environment is needed.

    The apt-cacher-ng is needed because, when I am doing the installation from the scratch the already synced repos could not be used.
    There are no kickstarter repos available. The repos could only be used when the server is already registered in the SUSE Manager.

    So I do the initial install using the apt-cache-ng on top SUSE Manager and after this I register to SUSE Manager.

    Yes, you are right, I saw the release note about 4.0.5 but I did not found the documentation about the provisioning_api. Is there a special section in the Manual?

    thanks a lot.
    Franz

  • Leave a Reply

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