Support Policies for RHEL High Availability clusters - fence_vmware_rest
Contents
Overview
Applicable Environments
- Red Hat Enterprise Linux (RHEL) 7 with the High Availability Add-On
- Using a VMware virtualization product vsphere 6.5 and newer versions
Recommended Prior Reading
Useful References and Guides
- Support Policies for RHEL High Availability Clusters
- How do I configure a stonith device using agent fence_vmware_rest in a RHEL 7 or 8 High Availability cluster with pacemaker ?
Introduction
This guide offers Red Hat's policies and requirements for using the fence_vmware_rest fence-agent for RHEL High Availability clusters running on VMware platforms. Users of RHEL High Availability clusters should adhere to these policies in order to be eligible for support from Red Hat with the appropriate product support subscriptions.
Policies
Supported releases for fence_vmware_rest: Red Hat supports the usage of fence_vmware_rest as a STONITH agent for RHEL High Availability clusters with VMware VMs as of RHEL 7 Update 5 with fence-agents-4.0.11-86.el7 and later. Earlier releases of RHEL do not have support from Red Hat for using the vSphere REST API for fencing of cluster nodes.
Availability of vSphere Automation SDK for REST: The fence_vmware_rest agent is only functional in vSphere environments that provide the REST API from VMware's vSphere Automation SDK for REST. This SDK is only available for certain releases of vSphere - starting with 6.5. Thus, fence_vmware_rest is not supported with older releases of vSphere or with VMware environments that do not make this REST API available.
Supported VMware platforms and releases: Refer to Red Hat's support policies regarding VMware virtual machines in RHEL High Availability clusters for details on which VMware products, versions, and conditions are tested:
Red Hat's support of fence_vmware_rest is limited to those listed combinations. If a problem is identified with an alternate configuration, Red Hat's assistance may be limited to migration to one of those supported combinations. Red Hat will accept reports of defects or concerns with alternate combinations, but will use its own discretion in deciding whether and on what timeline to address such concerns.