Hi Guillaume,
 As Satheesaran suggested the possible options which is completly valid points. Thanks sas for that.
I would suggest to wait till 4Kn validation complet with Gluster + VDO (All usecases), if you want 4K support. Other wise you can go ahead with emulate512=on .

On Tue, Oct 1, 2019 at 11:56 AM Satheesaran Sundaramoorthi <sasundar@redhat.com> wrote:
On Tue, Oct 1, 2019 at 11:27 AM Guillaume Pavese <guillaume.pavese@interactiv-group.com> wrote:
Hi all,

Sorry for asking again :/

Is there any consensus on not using --emulate512 anymore while creating VDO volumes on Gluster?
Since this parameter can not be changed once the volume is created and we are nearing production setup. I would really like to have an official advice on this.

Best,

Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group

Hello Guillaume Pavese,
If you are not using --emulate512 for VDO volume, then VDO volume will be created
as 4K Native volume (with 4K block size).

There are couple of things that bothers here:
1. 4K Native device support requires fixes at QEMU that will be part of
CentOS 7.7.2 ( not yet available )
2. 4K Native support with VDO volumes on Gluster is not yet validated
thoroughly.

Based on the above items, it would be better you have emulate512=on or delay
your production setup ( if possible, till above both items are addressed )
to make use of 4K VDO volume.

@Sahina Bose Do you have any other suggestions ?

-- Satheesaran S (sas)

On Fri, Sep 27, 2019 at 3:19 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:


Il giorno ven 27 set 2019 alle ore 05:21 Guillaume Pavese <guillaume.pavese@interactiv-group.com> ha scritto:
I see that oVirt 4.3.6 finally has 4k domain support. 

- Would that mean that VDO enabled Gluster domains will be created without the --emulate512 workaround?
- If the wizard to create the Gluster volumes has not yet removed that parameter, is it safe to edit & remove it manually before creation?
- Should we expect performance increase by using the native 4k block size of VDO?



 
Thanks

Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group


On Fri, Sep 27, 2019 at 12:00 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

The oVirt Project is pleased to announce the general availability of oVirt 4.3.6 as of September 26th, 2019.

 

This update is the sixth in a series of stabilization updates to the 4.3 series.

 

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

 

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)

 

Due to Fedora 28 being now at end of life this release is missing experimental tech preview for x86_64 and s390x architectures for Fedora 28.

We are working on Fedora 29 and 30 support and we may re-introduce experimental support for Fedora in next release.

 

See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed.

 

Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


oVirt Node and Appliance have been updated including:

- oVirt 4.3.6: http://www.ovirt.org/release/4.3.6/

- Wildfly 17.0.1: https://wildfly.org/news/2019/07/07/WildFly-1701-Released/

- Latest CentOS 7.7 updates including:

- latest CentOS Virt and Storage SIG updates:


 

Given the amount of security fixes provided by this release, upgrade is recommended as soon as practical.


Additional Resources:

* Read more about the oVirt 4.3.6 release highlights:http://www.ovirt.org/release/4.3.6/

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:http://www.ovirt.org/blog/

 

[1] http://www.ovirt.org/release/4.3.6/

[2] http://resources.ovirt.org/pub/ovirt-4.3/iso/

--
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AY66CEQHHYOVBWAQQYYSPEG5DXEIUAAT/

Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. 



--

Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. 



--


Thanks,
Gobinda