On 2021-08-27 13:24, Thomas Hoberg wrote:
I'd rather doubt the GUI would help you there and what's worse, the GUI doesn't easily tell you what it tries to do. By the time you've found and understood what it tries from the logfiles, you'd have it done on your own.
It's an unfortunate thing that the GUI assumptions can be counter intuitive in many regards, but i can confirm you can do this in the GUI as long as the gluster volumes was created in the GUI in the first place. If not, it will not show up as a volume.
Now whether or not oVirt will then treat such a hand-made 1->3 node cluster like a 3 node HCI built by itself is something I've never tried.
It will as long as the above gluster volume requirement is met, although if using gluster for hosted engine you typically end up doing that by hand.
If I had successfully tested the 3 node to 6 and 9 node expansion, I'd perhaps be more confident. But it could just turn out that without fiddling with the postgres database in the management engine this won't happen.
I do this quite often, add hosts to compute, add bricks to a gluster volume, done deal. However we do tend to use ZFS underneath which is outside the scope of oVirt. It allows us to re-use existing storage elements (providing there is enough space) to create temporary volumes to assist in the process.
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/M5VC5AP6V6BV2VNQT46DKNF253W3ECPL/
