Please test the 5 nodes hybrid RHHI-V cluster configuration where 3 nodes are part of HCI, HE+gluster deployment, and the other two hosts added to the same cluster are plain RHV hypervisors, no gluster, no HE. All the 5 hosts are part of a single RHV cluster and can run the same VMs. The non HCI hosts will access the gluster storage domain provided by the HCI nodes as a regular storage domain. I am on the border if this is a test only scenario or an actual RFE.
(In reply to Marina Kalinin from comment #0) > Please test the 5 nodes hybrid RHHI-V cluster configuration where 3 nodes > are part of HCI, HE+gluster deployment, and the other two hosts added to the > same cluster are plain RHV hypervisors, no gluster, no HE. Clarification : the other 2 hosts added will have gluster services running, and will be part of gluster cluster. The only difference is they do not host any gluster volume bricks. > > All the 5 hosts are part of a single RHV cluster and can run the same VMs. > The non HCI hosts will access the gluster storage domain provided by the HCI > nodes as a regular storage domain. > > I am on the border if this is a test only scenario or an actual RFE.
Tested with RHV 4.4.1 (RHVH-4.4-20200722.1-RHVH-x86_64-dvd1.iso) and RHGS 3.5.2-async (glusterfs-6.0-37.1) 1. Created a 3 node RHHI-V/Hyperconverged deployment 2. Create 20 VMs and started kernel untar workload on all the VMs. 3. Added a 2 more compute-only node, with no bricks, with 'hosted-engine --deploy' 4. Migrated the VMs to new node. 5. Created few more HA VMs and ran it on the newly added compute only nodes 6. Powered off 2 of the nodes in the cluster and observed that everything worked properly Based on the above observations, verifying this bug
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHHI for Virtualization 1.8 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:3314