You create gluster as usual.
Install OS,
prepare the brick (disk alignment is very important), mount the brick (context= mount option is nice for SELINUX), then gluster peer probe the new host and then 'add-brick' to expand the volume.

hosted-engine deployment can be done on multiple storages (NFS, GlusterFS, SAN) and thus the 2 topics should not be confused.

The only requirement for the hosted-engine volume is to apply the 'virt' group of settings. Previously, there was a requirement that storage phisical blcok size should be 512, but that could have changed in the past years.

Best Regards,
Strahil Nikolov

On Mon, Jun 28, 2021 at 12:43, Harry O
<> wrote:
Should the engine not deploy gluster when host reinstall is ran? How do I deploy my gluster setup on a replacement node replacing a dead node?
Users mailing list --
To unsubscribe send an email to
Privacy Statement:
oVirt Code of Conduct:
List Archives: