Red Hat Gluster Storage Life Cycle

Overview

Red Hat has established specific life-cycle policies for the Red Hat Gluster Storage product to allow customers and partners to plan their test cycles, roll-outs, deployments, and implementations. This policy applies to all Red Hat Gluster Storage variants (e.g., on-premise and public cloud).

Details

Every major release of Red Hat Gluster Storage is supported, from the date of General Availability to the End of Life date stated in the Life Cycle Dates table below.

Note that the Red Hat Gluster Storage product has a defined support lifecycle through to 31-Dec-24, after which the Red Hat Gluster Storage product will have reached its EOL. Specifically, RHGS 3.5 represents the final supported RHGS series of releases. RHGS 3.5.x will continue to receive select updates through to its defined EOL date. RHGS releases prior to 3.5 are no longer supported. For any questions about the Red Hat Gluster Storage product support lifecycle or to explore your Red Hat modernization and migration options, please reach out to your Red Hat sales representative.

Software changes to Red Hat Gluster Storage are delivered via individual updates known as errata advisories. All errata updates are incremental and cumulative on the major release of the Red Hat Gluster Storage product. Errata advisories can be released individually on an as-needed basis or aggregated as a minor release or z-streams. New functionality is usually only included in minor releases but they are rarely included in z-streams based on customer demand and other considerations. Errata advisories may contain security fixes (Red Hat Security Advisories or RHSAs), bug fixes (Red Hat Bug Fix Advisories or RHBAs), or feature enhancements (Red Hat Enhancement Advisories or RHEAs).

All released errata advisories remain accessible to active subscribers for the entire Red Hat Gluster Storage life cycle. Within each major release of Red Hat Gluster Storage, any errata advisory (including one released as part of a minor release) will be applied cumulatively to the latest release of Red Hat Gluster Storage, including any patch sets. Minor and z-stream releases of Red Hat Gluster Storage do not restart the life cycle or initiate a new maintenance stream of updates. Minor and z-stream releases deliver only incremental and cumulative updates to the Red Hat Gluster Storage maintenance stream.

During the Life Cycle of major RHGS releases, customers are expected to update to new minor and z-stream releases as and when they become available. Accelerated Fixes will not be provided for issues that have already been fixed in the current release, and the customer is expected to upgrade to the latest release to get that fix. In circumstances where the reported issue is not fixed in the current shipping release, the customer is still expected to upgrade their systems to the latest release as the accelerated fix can be created and verified only against the latest or the immediately previous release.

The life cycle is divided into 2 phases: a Full Support Phase and a Maintenance Support Phase.

Full Support Phase

This phase begins with the GA of a major version of Red Hat Gluster Storage. During this period, Red Hat will deploy minor releases of Red Hat Gluster Storage, which will deliver new functionality and periodic asynchronous errata updates in between minor releases. The asynchronous updates will deliver Critical and Important Security errata advisories (RHSAs), and Urgent Priority Bug Fix errata advisories (RHBAs) as they are available.

Maintenance Support Phase

The last minor release will transition the life cycle from the Full Support Phase to the Maintenance Support Phase. During the Maintenance Support Phase, new functionality will not be delivered. However, Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) will continue to be issued as they are available.

Red Hat Storage 3.5 is the last minor release of Red Hat Gluster Storage 3.

RHEL support

From Red Hat Gluster Storage 3 (formerly Red Hat Storage Server 3) onward, the storage server will be supported on one or more versions of Red Hat Enterprise Linux. Red Hat will notify and detail which versions of RHEL support the storage server.

Security Updates

Throughout the support lifecycle, qualified security issues of Critical or Important impact, and select mission-critical bugs, will be addressed by updated packages. For more information on how the impact of security issues is assessed, please refer to Issue Severity Classification.

Following the RHS 3.0.4 release, the samba-3.x package shipped earlier at the primary RHS 3 RHN channel, and CDN repo will not receive any further updates, including security updates. All RHS customers who use samba are recommended to move to samba-4.x for continued support.

Following the update to RHGS 3 Samba on RHEL 7, the ctdb2.5 package shipped earlier at the primary RHGS 3 RHN channel, and CDN repo will not receive any further updates, including security updates. All RHGS customers who use ctdb are recommended to subscribe to RHGS Samba repo for continued support.

Following the RHGS 3.1.3 release, the packages needed for configuring High Availability (HA) for NFS Ganesha shipped earlier at the primary RHGS 3 RHN channel, and CDN repo will not receive any further updates, including security updates. All RHGS customers who use HA for NFS Ganesha are recommended to subscribe to the RHEL HA channel/repo for continued support.

Upgrade Process

Obtain updates from Red Hat's Content Delivery Network. Obtain security and bug fixes by using the yum command.

In-service updates to a new minor release are supported from the last two previous minor releases (n-2).

Note

We highly recommend updating your systems to latest versions regularly, in order to get the latest stability fixes and features.

Supported Hardware Configurations

Hardware must be selected from the supported configurations listed in the Red Hat Knowledgebase. This list will be updated and expanded as new models are qualified. Other configurations may be considered on a case-by-case basis.

Life Cycle Dates