Support Policies for RHEL High Availability Clusters - Subscriptions, Support Services, and Software Access

Updated -

Contents

Overview

Applicable Environments

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add-On

Useful References and Guides

Introduction

This guide describes Red Hat's policies and requirements regarding access to RHEL High Availability software repositories, and support services for that software.

Policies

Software repository access: Red Hat grants access to a repository containing RHEL High Availability software to Red Hat accounts that have valid RHEL High Availability Add-On subscriptions. RHEL servers can access software from these repositories by attaching to a subscription pool that contains such a RHEL High Availability subscription through Red Hat Subscription Manager. Once attached to such a pool, the "Red Hat Enterprise Linux High Availability (for RHEL X Server)" repository can be enabled to grant access to the software using yum or other package managers that interact with Red Hat repositories.


Subscriptions required for support services: Red Hat requires organizations to have valid, active subscription coverage for RHEL and the RHEL High Availability Add-On in order to have access to Red Hat support services for any High Availability software (see policies below for details on which components this applies to). The RHEL subscription that a High Availability Add-On subscription is associated with specifies the level of support that is to be granted to the organization in relation to RHEL High Availability software. Self-support RHEL subscriptions do not entitle an organization to receive assistance with RHEL High Availability from Red Hat Support.

Without a valid RHEL subscription that includes support services, Red Hat is unable to assist with the usage of RHEL High Availability software.


Number of subscriptions - every RHEL HA system must be covered: In order to receive assistance from Red Hat for any concern relating to the High Availability software running on any RHEL system, an organization must possess valid subscriptions for RHEL and the High Availability Add-On covering every member of the relevant cluster, and/or for any system that runs High Availability software. For instance:

  • If assistance is required with any member of a High Availability cluster, every member that participates in that cluster requires valid subscription coverage -
    whether that member is currently active or not at the time of the investigation. If the account's subscriptions do not cover all configured members of the cluster, then Red Hat cannot assist with concerns relating to that cluster.
  • Some components in the RHEL High Availability Add-On may be able to run on non-cluster members for the purpose of providing administrative functions or supplementary functions for a RHEL High Availability cluster. Any RHEL system that runs High Availability software must have valid subscription coverage in order to receive assistance from Red Hat, even if not a defined member of a cluster.
    • This includes systems running cluster-administration software like pcs or luci.
    • This includes systems running quorum services such as corosync-qnetd
    • This includes systems providing cluster arbitration such as with booth
    • This includes systems that serve as remote members with pacemaker_remote

RHEL High Availability components subject to these policies: The RHEL High Availability Add-On consists of numerous components (RPM packages) that may be distributed through various repositories or other avenues. The following components are considered to be part of the RHEL High Availability Add-On and are subject to the policies defined in this guide, as well as any other Red Hat policies targeting RHEL High Availability.

  • Any component that is obtained from a "Red Hat Enterprise Linux High Availability (for RHEL X Server)" repository provided by Red Hat Subscription Manager.
  • Any component that is listed in the Red Hat Customer Portal downloads section under the Red Hat Enterprise Linux High Availability product, for example here.
  • booth - And related subcomponents, including booth-arbitrator, booth-core, booth-site, booth-test
  • clufter - And related subcomponents, including clufter-bin, clufter-cli, clufter-common, clufter-lib-ccs, clufter-lib-general, clufter-lib-pcs, python-clufter
  • corosync - And related subcomponents, including corosync-qnetd, corosync-qdevice, corosynclib
  • fence-agents - And all related subcomponents and individual fence-agent packages
  • fence-virt - And all related subcomponents, including fence-virtd-multicast, fence-virtd-checkpoint, fence-virtd-libvirt
  • libqb
  • omping
  • pacemaker - And related subcomponents, including pacemaker-cli, pacemaker-cluster-libs, pacemaker-cts, pacemaker-doc, pacemaker-libs, pacemaker-nagios-plugins-metadata, pacemaker-remote
  • pcs
  • resource-agents - And related subcomponents, including resource-agents-sap, resource-agents-sap-hana
  • sbd
  • cluster - And related components, including cman, clusterlib, cluster-glue, cluster-glue-libs, cluster-snmp, cluster-cim
  • ccs - And related subcomponents, including ricci
  • luci
  • modcluster
  • omping
  • openais - And related subcomponents, including openaislib
  • rgmanager
  • Any development library or header library that is a child of one of the listed packages here (usually named component-devel, following its parent component).

Subscriptions and RHEL releases: RHEL and RHEL High Availability subscriptions enable support and access for versions of the RHEL High Availability software in accordance with Red Hat's RHEL Lifecycle and Production Support Scope of Coverage:

With a valid RHEL and RHEL High Availability subscription, Red Hat can provide assistance with RHEL High Availability releases that are in active production support phases according to the RHEL Lifecycle.


Comments