SUSE Manager 4.3 Public RC is out!
We are happy to announce our Public Release Candidate for SUSE Manager 4.3!
Beta Registration Codes
SLES 15 SP4 Public Beta is required as base OS, you will need to use the Online Installation Media (and not the Full Installation) or our Minimal-VM images (formely known as JeOS) for your virtual environment, you can retreive them from the link below.
Registration is not working with your regular SUSE Manager key, special Beta Registration Code is required! You need to request one via email to firstname.lastname@example.org
Reporting Database documentation
The reporting database provides SUSE Manager data used for reports in a simplified schema. It is accessible by any reporting tool with support for SQL databases as content source. This new database is created automatically, isolated and periodically updated from the one used for the SUSE Manager Server.
The tool uyuni-setup-reportdb-user can create new users who have read-only access to the data. For more information on this topic, see Hub reporting.
spacewalk-report and the reporting database
spacewalk-report will use the data from the report database by default. This change affects both new and updated setups. This means that the newly generated reports will differ in the structure and the format of the data and might break existing integrations. If this change causes trouble in your use case, the new option
--legacy-report can be used to fall back to the old report engine.
For a comprehensive list of what is changed and what reports are affected, see the section “Generate Reports” in the Administration Guide.
With SUSE Manager 4.3, it is now possible to migrate products even if the target product doesn’t have some of the successors. This is a common scenario in the case of LTSS, where migrating from an LTSS version to the target service pack does not yet have an LTSS module. Now it is up to the user to decide if they want to migrate or not. SUSE Manager will display enough information about the missing successors. Migrations are possible both with the webUI and the API.
Adding systems with failed actions to System Set Manager
It is now possible to select and add systems that failed or completed actions with a new button “Add Selected to SSM”. The scheduled actions shown in “Completed Systems” and “Failed Systems” now display this option. You can the find the actions in the Server WebUI using ‘Schedule’on the left navigation bar. This can be useful either to resolve issues with systems that failed to complete actions or to run more actions on those that completed them.
SCAP Security Guide support
SUSE provides the
scap-security-guide package to provide several openscap profiles. In the current version of scap-security-guide, SUSE supports the following profiles:
- DISA STIG profile for SUSE Linux Enterprise Server 12 and 15
- PCI-DSS profile for SUSE Linux Enterprise Server 12 and 15
- HIPAA profile for SUSE Linux Enterprise Server 12 and 15
Other profiles, like the CIS profile, are community-supplied and not officially supported by SUSE. For Non-SUSE OSs, please note that the included profiles are community supplied and not officially supported by SUSE.
spacewalk-clone-by-date has been deprecated
With SUSE Manager 4.3 release,
spacewalk-clone-by-date tool has been deprecated. With CLM (Content Lifecycle Management), SUSE Manager offers a superset of
spacewalk-clone-by-date, offering more flexibility and power. CLM provides a comprehensive API to cover all the important features that
spacewalk-clone-by-date tool offers with command-line and script integration. We highly encourage users to migrate their workload and scrips to CLM.
Additional documentation and examples will be provided to assist in transition.
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 Engineering and more.