It was this near endless range of possibilities via permutation of the parts
that originally attracted me to oVirt.
Being clearly a member of the original Lego generation I imagined how you could
simply add blocks of this and that to rebuild to something new fantastic...,
limitless gluster scal
Sadly, it's always 'It depends'.You definitely have to test with your workload.
One setup I see -> create a small replica volume for the OS of the VMs and a
second one (disperse volume) for the data disks.
Then, test and consider if it's enough for you.
Best Regards,Strahil Nikolov
On Tue, F
Thanks a lot, another reason alongside the storage overhead that led me to
erasure coding was the idle CPU cycles on our servers. Currently, we have
enough idle CPU cycles on our servers. Do you think erasure coding is a bad
choice even if we have enough idle CPUs?
__
Erasire coding is highly cpu intensive and usually it's not recommended for VMs.
You can create your own gluster volume [1] and then test your workload.
[1]
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/html/administration_guide/chap-red_hat_storage_volumes-creating_dis
4 matches
Mail list logo
