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_dispersed_volumes_1

Best Regards,
Strahil Nikolov

On Tue, Feb 1, 2022 at 11:33, alishirv--- via Users
<users@ovirt.org> wrote:
Hello everyone,

I'm new to oVirt. I want to set up a cost-efficient and fault-tolerant virtualization environment. Our VMs have low to medium IOPS, 70% of VMs have low IOPS and about 30% of them require about 5K IOPS. All the disks are NVMe. I found that the most cost-efficient storage plan in the current oVirt is a two-way replica with an arbiter and its storage overhead is more than 100%. As far as I know, we can use erasure coding with less storage overhead. Is there any plan to support erasure coding in oVirt? Would you even recommend erasure coding for VM workloads?

Best regards,
Ali
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/5HACZHHGJS7BL253PEA65FYAK7S4SDQL/