[ovirt-users] Re: Moving HostedEngine

2019-12-01 Thread Alan
The installation will fail if you attempt to install HE into an existing storage domain (or worse, it will corrupt the domain). As per the docs you will need a dedicated domain of at least 74GB for hosted_storage. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html

[ovirt-users] Re: Moving HostedEngine

2019-11-27 Thread Strahil
It is highly 'super duper' not recommended to do that. Also, consider using thinLVM (requirement for gluster snapshots) for a brick of the separate gluster volume. I'm using the 3rd partirion of my OS SSD to host my gluster's volume and I have no issues so far. Best Regards, Strahil NikolovOn

[ovirt-users] Re: Moving HostedEngine

2019-11-27 Thread Strahil
Hi Joseph, It is mandatory to create a dedicated gluster volume for the HostedEngine. There is a thread which explains why and the risks of not following these guidlines. You can set the volume on thinLVM, so you can snapshot your gluster's volume before patching of the engine (of course you h

[ovirt-users] Re: Moving HostedEngine

2019-11-27 Thread Joseph Goldman
So I can't host OTHER VM's on this gluster volume? If its already a running GLuser for other VMs i can't now re-reploy HE in that gluster volume? On 2019-11-28 3:27 AM, Alan G wrote: I've had to do this a couple of times and always ended up with a working system in the end. As a fall back op

[ovirt-users] Re: Moving HostedEngine

2019-11-27 Thread Alan G
I've had to do this a couple of times and always ended up with a working system in the end. As a fall back option (although I've never had to use it) I have a backup engine VM running completely outside of oVIrt (ESXi host in my case). Then if the hosted_engine deploy fails for any reason you