As CentOS Linux 7 approaches End of Life (EOL) on June 30, 2024, many organizations are exploring options and researching answers to frequently asked questions
- What do I do about the CentOS Linux 7 end of life in 2024?
- Can I migrate my devices to Red Hat Enterprise Linux (RHEL)?
- How do I evaluate the risk and uncertainty of migrating CentOS Linux 7 systems deployed in my environments?
At Red Hat, we've been listening, and offer multiple solutions to help you manage and maintain system deployments, both large and small.
Managing your CentOS Linux sprawl
Red Hat has enhanced and integrated the Convert2RHEL tool into 3 use cases. This article focuses on a fourth option: creating a dedicated conversion infrastructure with the help of Red Hat Insights, and using Red Hat Satellite for conversions at scale.
The Friday Five is a weekly Red Hat blog post with 5 of the week's top news items and ideas from or about Red Hat and the technology industry. Consider it your we ekly digest of things that caught our eye.
- Red Hat Extends Java Support in the Cloud with JBoss Enterprise Application Platform 8
- Why the future of manufacturing will rely on open source
- Schneider Electric Delivers Next-Generation, Open Automation Infrastructure in Collaboration with Intel and Red Hat
- DNEG transforms visual effects creation with Red Hat OpenShift, boosting artist productivity and data center efficiency
- Has AI Forced Banks to Collaborate?
Read on for details
The Red Hat Enterprise Linux (RHEL) web console is a simplified web-based management tool that lets you manage many aspects of RHEL more efficiently.
For more information on the web console and how to get started with it, refer to the Managing systems using the RHEL 9 web console documentation.
RHEL versions 9.3 and 8.9 have a number of new features and enhancements related to the web console, including:
- Several performance monitoring improvements
- Support for managing updates on RHEL for Edge systems (RHEL 9.3 only)
- Support for defining Podman container health check actions
- Improvements to the Accounts page that allow you to specify the home directory, shell, and user ID (UID) when creating accounts
- Improvements to virtual machine (VM) management
- Several enhancements to Stratis storage management
Performance monitoring improvements
The web console will now show the top services utilizing disk I/O resources on the system, which can help when troubleshooting performance issues. The following screenshot shows that the ubi9 Podman pod is the top service on the system utilizing disk I/O resources, and is writing 304 MB/s.
Red Hat Enterprise Linux (RHEL) is the world's leading enterprise Linux platform, known for its stability, versatility and enhanced security capabilities, whether on-premise or across the hybrid cloud.
To help RHEL users keep up with the latest updates and security patches, Red Hat has established a well-defined lifecycle for each RHEL version that helps customers to have a clearer understanding of the different support phases.
Let's start our overview from the beginning, outlining the different phases that constitute the RHEL lifecycle.
The trusted platform module (TPM) is a self-contained hardware encryption technology present in recent computer systems. It provides, among other things, hardware random number generation and more secure storage for encryption keys.
This enables administrators to encrypt operating system disks that will then only be decryptable on the same system. Version 2.0 of the TPM specification was published in 2015, and Microsoft's Windows 11 requires a version 2.0 TPM to be present to install.
To support operating systems like Windows 11 that require a TPM, libvirt provides a virtual TPM (vTPM) that can be configured with a virtual machine (VM) to provide the appearance of a hardware TPM. Red Hat OpenShift Virtualization has supported vTPM as an option since Red Hat OpenShift 4.13, with the persistent storage capability added in OpenShift 4.14.
Through open source innovation, Red Hat OpenShift has incrementally enabled Precision Time Protocol (PTP) use cases. Initially, an Ordinary Clock (OC) was provided in Red Hat OpenShift 4.7.
This supported a single follower clock port which synchronized the system clock to an upstream time leader system. This functionality used the open source driver and hardware provided by Intel for the x710 Fortville Network Interface Card (NIC) and the ptp4l and phc2sys software elements from the Linux PTP Project. Eventually, this evolved to support the Boundary Clock (BC) use case in Red Hat OpenShift 4.9.
The purpose of this article is to describe a solution to an issue that you may have faced when using Red Hat OpenShift Data Foundation in a cloud environment.
Specifically, we're looking at how to address the demand for more resources, more nodes and more Object Storage Devices (OSDs) as an OpenShift Data Foundation deployment matures.
In this article you'll find a step-by-step procedure in order to migrate the data from the existing OSDs to new ones with a bigger size, in order to manage more data with the same resources.
See all Archived Red Hat News articles
See all articles from this issue