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(a)redhat.com> wrote:
On Tue, Oct 1, 2019 at 11:27 AM Guillaume Pavese <
guillaume.pavese(a)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 <sabose(a)redhat.com> Do you have any other suggestions ?
-- Satheesaran S (sas)
>
> On Fri, Sep 27, 2019 at 3:19 PM Sandro Bonazzola <sbonazzo(a)redhat.com>
> wrote:
>
>>
>>
>> Il giorno ven 27 set 2019 alle ore 05:21 Guillaume Pavese <
>> guillaume.pavese(a)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?
>>>
>>>
>>
>> +Nir Soffer <nsoffer(a)redhat.com> +Sundaramoorthi, Satheesaran
>> <sasundar(a)redhat.com> +Gobinda Das <godas(a)redhat.com> can you answer
>> here?
>>
>>
>>
>>> Thanks
>>>
>>> Guillaume Pavese
>>> Ingénieur Système et Réseau
>>> Interactiv-Group
>>>
>>>
>>> On Fri, Sep 27, 2019 at 12:00 AM Sandro Bonazzola
<sbonazzo(a)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:
>>>>
>>>> -
>>>>
>>>> Release for CentOS Linux 7 (1908) on the x86_64 Architecture
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023405....
>>>> -
>>>>
>>>> CEBA-2019:2601 CentOS 7 NetworkManager BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023423....
>>>>
>>>> -
>>>>
>>>> CEBA-2019:2023 CentOS 7 efivar BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023445....
>>>> -
>>>>
>>>> CEBA-2019:2614 CentOS 7 firewalld BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023412....
>>>> -
>>>>
>>>> CEBA-2019:2227 CentOS 7 grubby BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023441....
>>>> -
>>>>
>>>> CESA-2019:2258 Moderate CentOS 7 http-parser Security Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023439....
>>>> -
>>>>
>>>> CESA-2019:2600 Important CentOS 7 kernel Security Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023444....
>>>> -
>>>>
>>>> CEBA-2019:2599 CentOS 7 krb5 BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023420....
>>>> -
>>>>
>>>> CEBA-2019:2358 CentOS 7 libguestfs BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023421....
>>>> -
>>>>
>>>> CEBA-2019:2679 CentOS 7 libvirt BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023422....
>>>> -
>>>>
>>>> CEBA-2019:2501 CentOS 7 rsyslog BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023431....
>>>> -
>>>>
>>>> CEBA-2019:2355 CentOS 7 selinux-policy BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023432....
>>>> -
>>>>
>>>> CEBA-2019:2612 CentOS 7 sg3_utils BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023433....
>>>> -
>>>>
>>>> CEBA-2019:2602 CentOS 7 sos BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023434....
>>>>
>>>> -
>>>>
>>>> CEBA-2019:2564 CentOS 7 subscription-manager BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023435....
>>>> -
>>>>
>>>> CEBA-2019:2356 CentOS 7 systemd BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023436....
>>>> -
>>>>
>>>> CEBA-2019:2605 CentOS 7 tuned BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023437....
>>>> -
>>>>
>>>> CEBA-2019:2871 CentOS 7 tzdata BugFix Update
>>>>
<
https://lists.centos.org/pipermail/centos-announce/2019-September/023450....
>>>>
>>>> - latest CentOS Virt and Storage SIG updates:
>>>>
>>>> -
>>>>
>>>> Ansible 2.8.5:
>>>>
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v...
>>>> -
>>>>
>>>> Glusterfs 6.5:
>>>>
https://docs.gluster.org/en/latest/release-notes/6.5/
>>>> -
>>>>
>>>> QEMU KVM EV 2.12.0-33.1 :
>>>>
https://cbs.centos.org/koji/buildinfo?buildID=26484
>>>>
>>>>
>>>>
>>>>
>>>> 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/
>>>>
>>>> --
>>>>
>>>> Sandro Bonazzola
>>>>
>>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>>>
>>>> Red Hat EMEA <
https://www.redhat.com/>
>>>>
>>>> sbonazzo(a)redhat.com
>>>> <
https://www.redhat.com/>*Red Hat respects your work life balance.
>>>> Therefore there is no need to answer this email out of your office
hours.
>>>> <
https://mojo.redhat.com/docs/DOC-1199578>*
>>>> _______________________________________________
>>>> Users mailing list -- users(a)ovirt.org
>>>> To unsubscribe send an email to users-leave(a)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/AY66CEQHHYO...
>>>>
>>>
>>> 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.
>>> <
https://interactiv-group.com/disclaimer.html>
>>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>
>> Red Hat EMEA <
https://www.redhat.com/>
>>
>> sbonazzo(a)redhat.com
>> <
https://www.redhat.com/>*Red Hat respects your work life balance.
>> Therefore there is no need to answer this email out of your office hours.
>> <
https://mojo.redhat.com/docs/DOC-1199578>*
>>
>
> 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.
> <
https://interactiv-group.com/disclaimer.html>
>