Hi Arik,
I don’t see an option to select ‘allocation-policy=clone and specifying that
the VM disk(s) should be preallocated’ when creating a VM from the template.
Regard
Simon
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to
On Fri, 11 Mar 2022, Abe E wrote:
Has anyone setup hype converged gluster (3Nodes) and then added more
after while maintaining access to the engine?
I have added additional self-hosted-engine hosts to a cluster in 4.3 and
it worked fine. I don't know if 4.4 is more strict about that or not,
If you are trying to re-use the existing bricks (gluster hosts) for
both clusters, you could potentially do it by making a seperate volume
on each brick. Then just have both clusters use their own specific
volume.
Underneath the volumes could have different physical media backing
them, or if
Has anyone setup hype converged gluster (3Nodes) and then added more after
while maintaining access to the engine?
An oversight on my end was 2 fold, Engine gluster being on engine nodes and new
nodes requiring their own cluster due to different CPU type.
So basically I am trying to see if I
Thanks for the reply.
Yes I was able to make it work in the end, for some reason Ovirt didnt
recognize the QCOW or Raw files as they were, so instead I took the vmdk my
vendor provided me and converted it to qcow and ovirt then recognized it
correctly.
Another one might be to import the OVA as a template and then provision a
VM from that template with allocation-policy=clone and specifying that the
VM disk(s) should be preallocated
On Fri, Mar 11, 2022 at 7:56 AM Strahil Nikolov via Users
wrote:
> One workaround that comes to my mind is to
6 matches
Mail list logo
