Show Table of Contents
2.2. Compatible Versions
The following table indicates the product and package versions required to create a supported deployment of Red Hat Gluster Storage (RHGS) nodes managed by the specified version of Red Hat Enterprise Virtualization (RHEV).
Table 2.1. Supported version information for Red Hat Gluster Storage
| RHGS version | gluster version | gluster op-version | RHEV version |
|---|---|---|---|
| 3.0 | 3.6.0.28-1 | 30000 | 3.4 |
| 3.0 Update 1 | 3.6.0.29-1 | 30000 | 3.4 |
| 3.0 Update 2 | 3.6.0.29-3 | 30000 | 3.4 |
| 3.0 Update 3 | 3.6.0.42-1 | 30000 | 3.4 |
| 3.0 Update 4 | 3.6.0.53-1 | 30004 | 3.5 |
| 3.1 | 3.7.1-11 | 30703 | 3.5, 3.6 |
| 3.1 Update 1 | 3.7.1-16 | 30703 | 3.5, 3.6 |
| 3.1 Update 2 | 3.7.5-19 | 30707 | 3.5, 3.6 |
Red Hat Enterprise Virtualization uses a compatibility version to indicate the version of Red Hat Enterprise Virtualization that the data center is intended to be compatible with. This compatibility level must be the same throughout the cluster. Use the following table to determine an appropriate compatibility version for your versions of Red Hat Enterprise Virtualization and Red Hat Gluster Storage.
Table 2.2. Cluster compatibility matrix
| RHEV Version | RHGS Version | Cluster Compatibility |
|---|---|---|
| 3.4 | 3.0.z | 3.4 |
| 3.1.z | 3.4 | |
| 3.5 | 3.0, 3.0.1, 3.0.2, 3.0.3 | 3.4 |
| 3.0.4 | 3.5 | |
| 3.1.z | 3.5 | |
| 3.6 | 3.0.z | 3.4 |
| 3.1.z | 3.5 |
Red Hat Enterprise Virtualization 3.6 requires a compatibility setting of 3.5 when used with Red Hat Gluster Storage 3.1 because Red Hat Gluster Storage does not currently include the vdsm package required to support a compatibility version of 3.6.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.