Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
Chapter 24. System roles
The following chapter contains the most notable changes to system roles between RHEL 8 and RHEL 9.
24.1. Performing system administration tasks with RHEL system roles
As of Red Hat Enterprise Linux 9.0 General Availability (GA) release, RHEL system roles includes the ansible-core 2.12 package. This is a version of Ansible that has only the core functionality - that is, it does not include modules such as blivet for the storage role, gobject for the network role, and plugins such as json_query.
With RHEL system roles, you can take advantage of a configuration interface to remotely manage multiple RHEL systems. As an option to the traditional RHEL system roles format, you can benefit from Ansible Collections, available in the Automation Hub only for Ansible Automation Platform Customers or via RPM package, available for RHEL users.
RHEL system roles support
Support for the following roles are available:
-
The
cockpitRHEL system role. You can automate the deployment and configuration of the web console and, thus, be able to manage your RHEL systems from a web browser. -
The
firewallRHEL system role. -
The
ha_clusterRHEL system role, formerly presented as a Technology Preview, is now fully supported. -
The
gfs2RHEL system role, which creates Red Hat Global File System 2 (GFS2) file systems in a Pacemaker cluster managed with thepcscommand-line interface. Previously, setting up GFS2 file systems in a supported configuration required you to follow a long series of steps to configure the storage and cluster resources. Thegfs2role simplifies the process. Using the role, you can specify only the minimum information needed to configure GFS2 file systems in a RHEL high availability cluster. -
The
nbde_clientRHEL system role now supports servers with static IP addresses. -
The Microsoft SQL (
microsoft.sql.server) role for Microsoft SQL Server. It simplifies and automates the configuration of RHEL with recommended settings for MSSQL Server workloads. Currently, the SQL Server does not support running on RHEL 9. You can only run the role on a RHEL 9 control node to manage the SQL Server on RHEL 7 and RHEL 8. -
The
VPNRHEL system role, to configure VPN connections on RHEL systems by using Red Hat Ansible Automation Platform. Users can use it to set up host-to-host, network-to-network, VPN Remote Access Server, and Mesh configurations. -
The
IPMImodules, to automate hardware management interfaces available in therhel_mgmtCollection. -
The
keylime_server, to configure and deploy the server components for Keylime Remote Attestation.
To learn more about the RHEL system roles, see the documentation title Administration and configuration tasks using system roles in RHEL.
Support for Ansible Engine 2.9 is no longer available in RHEL 9
Ansible Engine 2.9 is no longer available in Red Hat Enterprise Linux 9. Playbooks that previously ran on Ansible Engine 2.9 might generate error messages related to missing plugins or modules. If your use case for Ansible falls outside of the limited scope of support for Ansible Core provided in RHEL, contact Red Hat to discuss the available offerings.
RHEL system roles now uses Ansible Core
As of the RHEL 9 General Availability release, Ansible Core is provided with a limited scope of support to enable RHEL supported automation use cases. Ansible Core is available in the AppStream repository for RHEL. For details on the scope of support, refer to Scope of support for the Ansible Core package included in the RHEL 9 AppStream.
As of Red Hat Enterprise Linux 9.0, the scope of support for Ansible Core in the RHEL AppStream is limited to any Ansible playbooks, roles, and modules that are included with or generated by a Red Hat product, such as RHEL system roles.
The deprecated --token option of the subscription-manager register command will stop working at the end of November 2024
The default entitlement server, subscription.rhsm.redhat.com, will no longer be allowing token-based authentication from the end of November 2024. As a result, the deprecated --token=<TOKEN> option of the subscription-manager register command will no longer be a supported authentication method. As a consequence, if you use subscription-manager register --token=<TOKEN>, the registration will fail with the following error message:
Token authentication not supported by the entitlement server
To register your system, use other supported authorization methods, such as including paired options --username / --password OR --org / --activationkey with the subscription-manager register command.
RHEL system roles can be used to manage multiple different versions of RHEL
You can use RHEL system roles as a consistent interface to manage different versions of RHEL. This can help to ease the transition between major versions of RHEL.
RHEL 8 moves to Maintenance Support phase
After the RHEL 8.10 release, RHEL 8 moved to the Maintenance Support phase and will no longer receive new features. As a result, starting with RHEL 9.5, new features will only be available in RHEL 9. Therefore, to get access to the latest enhancements use RHEL 9 for your RHEL system role control nodes.
