Re: [ovirt-users] recommendations for best performance and reliability

On Mon, Nov 13, 2017 at 3:33 PM, Rudi Ahlers <rudiahlers(a)gmail.com&gt; wrote: All 3 servers need to be on the same network with low latency between servers. Gluster volume is used in replica 3 configuration in oVirt, and data will be written to all 3 servers synchronously. If you have one of the 3 servers in a remote location, your writes will be slow and the storage will seem to be unavailable to oVirt. For Disaster recovery, you can use gluster's geo-replication feature. This does need an additional server in the remote location. See https://www.ovirt.org/develop/release-management/features/gluster/gluster... Replica 3 gluster volume with sharding turned on for the gluster volume. If you use the deployment via Cockpit option, the volume is created with all recommended options. You can also manually set this by enabling the virt profile, like this # gluster volume set <volumename> group virt Gluster can work with either RAID or JBOD ( with replica 3, JBOD can be used, as gluster has the redundancy built in on the other nodes). Users often choose RAID to aggregate capacity from multiple disks as single brick, and also as the brick rebuilt time is offloaded to RAID layer in case of any of the hard disk failures. The answer is it depends on your needs and the hardware you have. That's correct. With a replica 3 approach, the oVirt environment is available even when one of the 3 hosts fail.