[ovirt-users] Re: Libgfapi considerations

It would be nice to see some progress. I have no idea why there wouldn’t be interest in adding to rhev. The io performance increase I saw while testing was phenomenal On Wed, Dec 18, 2019 at 9:42 PM Guillaume Pavese < guillaume.pavese(a)interactiv-group.com&gt; wrote: > The bug has been closed wontfix for a lack of perceived progress on the > issue : > https://bugzilla.redhat.com/show_bug.cgi?id=1633642 > https://bugzilla.redhat.com/show_bug.cgi?id=1484227 > > However when following the related opened bugs in qemu, i get the feeling > things are getting ready to have libgfapi working in a replica 3 cluster. > See : https://bugzilla.redhat.com/show_bug.cgi?id=1465810 > > I wish someone would reopen those closed bugs in order for that issue not > being forgotten. > > Guillaume Pavese > Ingénieur Système et Réseau > Interactiv-Group > > > On Tue, Dec 17, 2019 at 7:21 AM Jayme <jaymef(a)gmail.com&gt; wrote: > >> I believe the snapshot issue is only present with gluster replica 3 >> volumes. I can confirm it on my replica 3 cluster >> >> On Mon, Dec 16, 2019 at 4:18 PM Alex McWhirter <alex(a)triadic.us&gt; wrote: >> >>> I also use libgfapi in prod. >>> >>> >>> 1. This is a pretty annoying issue, i wish engine-config would look to >>> see if it already enabled and just keep it that way. >>> >>> 2. Edit /etc/libvirt/qemu.conf and set dynamic ownership to 0, will >>> stop the permission changes. >>> >>> 3. I don't see this error on any of my clusters, all using libgfapi. >>> >>> >>> I also have no issues using snapshots with libgfapi, but live migration >>> between storage domains indeed does not work. >>> >>> >>> On 2019-12-16 12:46, Darrell Budic wrote: >>> >>> I use libgfap in production, the performance is worth a couple of >>> quirks for me. >>> >>> - watch major version updates, they'll silently turn it off because the >>> engine starts using a new version variable >>> - VM/qemu security quirk that resets ownership when the VM quits, was >>> supposedly fixed in 4.3.6 but I still have it happen to me, a cron'd chown >>> keeps it under control for me >>> - some VMs cause a libvirt/vdsmd interaction that results in failed >>> stats query, and the engine thinks my VMs are offline because the stats >>> gathering is stuck. hoped a bug fix in 4.3.6 would take care of this too, >>> but didn't. may be my VMs though, still analyzing for specific file issues >>> >>> I need to spend some time doing a little more research and >>> filing/updating some bug reports, but it's been a busy end of year so far... >>> >>> -Darrell >>> >>> On Dec 14, 2019, at 5:47 PM, Strahil Nikolov <hunter86_bg(a)yahoo.com&gt; >>> wrote: >>> >>> >>> According to GlusterFS Storage Domain >>> <https://www.ovirt.org/develop/release-management/features/storage/gluster... >>> >>> the feature is not the default as it is incompatible with Live Storage >>> Migration. >>> >>> Best Regards, >>> Strahil Nikolov >>> >>> >>> В събота, 14 декември 2019 г., 17:06:32 ч. Гринуич+2, Jayme < >>> jaymef(a)gmail.com&gt; написа: >>> >>> >>> Are there currently any known issues with using libgfapi in the latest >>> stable version of ovirt in hci deployments? I have recently enabled it and >>> have noticed a significant (over 4x) increase in io performance on my vms. >>> I'm concerned however since it does not seem to be an ovirt default >>> setting. Is libgfapi considered safe and stable to use in ovirt 4.3 hci? >>> _______________________________________________ >>> 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/FYVTG3NUIXE... >>> _______________________________________________ >>> 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/NDZD4W5UYYR... >>> >>> >>> _______________________________________________ >>> 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/6KAWATJCAON... >>> >>> >>> _______________________________________________ >>> 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/LLLC3CMLWGS... >>> >> _______________________________________________ >> 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/GNMWDCNGJYN... >> > > 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> >