It's not outdated but it's rarely necessary because:- the HostedEngine volume 
must be dedicated for the HE VM. Setting enough space for the bricks is enough 
- for example physical disk is 100GB, Thinpool is 100GB, thin LV 84GB (16GB 
should be put aside for the metadata). In such configuration, you can't go out 
of space.I/O overhead can be minimized by setting the full stripe size (and the 
thinpool chunk size) between 1MiB and 2MiB (preferably in the lower end).
One big advantage of the thinpool-based bricks is that you can create snapshots 
of the volume. Usually I shut down the engine, snapshot the volume and then 
power up and do the necessary actions (for example Engine upgrade).
Best Regards,Strahil Nikolov 
 
 
  On Sun, Sep 18, 2022 at 22:50, Jonas<jo...@rabe.ch> wrote:   

https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html/deploying_red_hat_hyperconverged_infrastructure_for_virtualization/rhhi-requirements#rhhi-req-lv

> The logical volumes that comprise the engine gluster volume must be thick 
> provisioned. This protects the Hosted Engine from out of space conditions, 
> disruptive volume configuration changes, I/O overhead, and migration activity.

Or is that extremely dated information?

Am 18. September 2022 21:08:45 MESZ schrieb Strahil Nikolov via Users 
<users@ovirt.org>:
>Can you share the RH recommendation to use Thick LV ?
>Best Regards,Strahil Nikolov  
> 
>    I don't have that anymore, but I assume that gluster_infra_lv_logicalvols 
>requires a thin pool: 
>https://github.com/gluster/gluster-ansible-infra/blob/master/roles/backend_setup/tasks/thin_volume_create.yml
>_______________________________________________
>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/XQ4Q4SELENO6EMF4WUQKM27G55RPEM3O/
>  
_______________________________________________
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/I3Z7QEY4CMZD5QFGFGMNABHVAGHK5IWU/
  
_______________________________________________
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/RBDBPEVGJLKB4XLYWCN4BJTPW4WYG43J/

Reply via email to