How does Red Hat Hyperconverged Infrastructure (RHHI) support work?

Solution Verified - Updated -


  • Red Hat Virtualization (RHV) 4.4 with Red Hat Hyperconverged Infrastructure for Virtualization (RHHI-V) 1.8
  • RHV 4.3 with RHHI 1.7


  • How does Red Hat Hyperconverged Infrastructure work, both in terms of entitlements needed as well as layering of Red Hat Virtualization plus its guests and Red Hat Storage?


  • Red Hat Hyperconverged Infrastructure (RHHI) is an offering based on Red Hat Virtualization (RHV) and Red Hat Gluster Storage (RHGS).

  • The only supported way to use RHV hosts as Hyperconverged (i.e. to provide Red Hat Storage and Virtualization capabilities at the same time) is through RHHI deployment following RHHI-V official documentation.

    • The supported hosts are RHVH hosts only (not RHEL hosts).
    • RHGS version should match with the corresponding version shipped with RHVH. No manual updates of glusterfs packages allowed.
    • Max of 12 nodes in the cluster, in increments of three: 3, 6, 9, 12.
    • All hosts should be part of both the virt cluster and gluster trusted storage pool.
    • The nodes in the virt cluster should be the same set of nodes available in gluster cluster as well.
    • SHE deployment mode, no standalone RHV Manager allowed.
  • A RHHI-V entitlement is needed as well. It isn't supported to run a RHHI environment with just RHV + RHGS entitlements; though using Red Hat Gluster Storage for simply hosting RHV guests, i.e. to use RHGS as a RHV Storage Domain, running on a different server, is fine.

  • RHHI-V Version Compatibility matrix.

  • RHHI-V Life Cycle

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.


Not helpful as technology not available