With Gluster gone, you could still use SAN and NFS storage, just like before they tried to compete with Nutanix and vSphere. Can you imagine IBM sponsoring oVirt, which doesn't make any money without RHV, which evidently isn't profitable enough? Most likely oVirt will lead RHV, in this case to the scrapyard, by months if not years.

Hi all, or maybe https://linbit.com/linstor/  ? We too are in dilemma what to do with our RHV/oVirt production environment. I have small 6 node HCI installation in my lab with linstor and so far I'm impressed. If oVirt had support for linstor we would certainly continue to use oVirt (even after EOL of RHV), but now we are considering to move away to something that has support for linstor (Proxmox, OpenNebula, ...) I have seen that there was some consideration of use of DRBD with oVirt ( https://www.ovirt.org/develop/release-management/features/infra/drbd.html ). I guess linstor makes this easier now. Best regards Dori On 2/4/22 17:53, Leo David wrote:

Maybe its a perfect time to add ( again ) Ceph into discution.

Leo

On Fri, Feb 4, 2022, 18:21 Thomas Hoberg <thomas@hoberg.net> wrote:

With Gluster gone, you could still use SAN and NFS storage, just like before they tried to compete with Nutanix and vSphere.

Can you imagine IBM sponsoring oVirt, which doesn't make any money without RHV, which evidently isn't profitable enough?

Most likely oVirt will lead RHV, in this case to the scrapyard, by months if not years. _______________________________________________ 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/T64IKY4DQUPQJX...

_______________________________________________ Users mailing list --users@ovirt.org To unsubscribe send an email tousers-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/GAWGUIQ7A36G6O...

I don't want to be anybody's  advocate here. And I also found DRBD alone too cumbersome to use in this role in the past, but linstor actually makes it very easy to use. In search for HCI storage solution I was convinced by following press release ( https://linbit.com/blog/iops-world-record-broken-linbit-tops-14-8-million-io... ) to even try linstor  (I am glad I did). I can not speak about CEPH but Gluster performance was always problematic for us. Please do not understand me wrong. I think more choices of storage is a good thing and makes oVirt a more viable solution. There are other solutions out there which adopt new storage options faster and if oVirt will fall too far behind imho it would certainly not be good. Best regards, Dori On 2/4/22 20:27, Strahil Nikolov via Users wrote:

RHV & RHGS might be abandoned, but this doesn't mean that oVirt & Gluster should stop existing just because a corporation doesn't see HugePiles of $ in them. Removing Gluster support from oVirt, just because RHGS support is close to end, is irrelevant. After all, oVirt never had support in the full meaning of it.

It is up to the community and despite the  future doesn't seem bright, I don't see how Openshift will take oVirt/RHV's place and I don't want to go back to KVM + Pacemaker .

I was searching for alternatives for a small Hyperconverged setup and to be honest, neither CEPH, nor DRBD look so useful.

Best Regards, Strahil Nikolov

On Fri, Feb 4, 2022 at 19:28, Dori Seliškar via Users <users@ovirt.org> wrote: _______________________________________________ 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/SJXJV7442IV4OI...

_______________________________________________ Users mailing list --users@ovirt.org To unsubscribe send an email tousers-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/5IUFP5ZVJHJLFK...

Please have a look here: https://access.redhat.com/support/policy/updates/rhev/ Without a commercial product to pay the vast majority of the developers, there is just no chance oVirt can survive (unless you're ready to take over). RHV 4.4 full support ends this August and that very likely means that oVirt won't receive updates past July (judging by how things happened with 4.3). And those will be CI tested against the Stream Beta not EL8 including RHEL. Only with a RHV support contract ($) you will receive service until 2024 and with extended support ($$$) until 2026. oVirt is dead already. They have known since October. They should have told us last year.

Il giorno sab 5 feb 2022 alle ore 13:30 Nathanaël Blanchet <blanchet@abes.fr> ha scritto:

Can anybody from redhat confirm what is supposed here, all my staff depends on the future of ovirt. How can we help to maintain this project alive if redhat dev are not implicated anymore? I may donate some hardware or is it unuseful?

Looks like this is being asked on several channels so I guess I'll end up writing a blog post or add some statement on the oVirt home page. Anyway, let me reiterate the message: This has been discussed publicly ( https://lists.ovirt.org/archives/list/users@ovirt.org/message/VIYHOW3WDR6N4A... ) As a product, Redhat Virtualization has a different lifecycle than oVirt which is a community project. What will be the future of oVirt project depends on how the community will be shaping it. As members of the Red Hat team working on the oVirt project we are actively doing whatever we can to ensure that the project will survive after we'll stop working on it in the future. - We are moving the development to public platform (GitHub) - We are changing our release process to ship oVirt builds via widely supported community systems like Fedora COPR and CentOS CBS. - We started a peering program helping whoever would like to start having an active role in oVirt community trying to make the onboarding as easy as possible ( https://lists.ovirt.org/archives/list/users@ovirt.org/message/QQVZHTFBF7NVI6... ) - We actively reached out to Rocky Linux, Alma Linux and Oracle, trying to engage them (CentOS is already engaged providing Community Build System for Virtualization SIG). So, what will be the future of the oVirt project depends on how the community will be shaping it. You're welcome to contribute to shaping this future! https://ovirt.org/develop/ Up to now: - We have one person who reached out being interested to the peering program, Maithreyi Gopal ( https://lists.ovirt.org/archives/list/devel@ovirt.org/message/TSSE7U36UQTEGE... ) and she's been peered with @Sanja Bonic <sbonic@redhat.com> . - Rocky Linux replied they were discussing within the Foundation meeting about oVirt but I didn't got the result of the discussion yet. - Oracle replied they are looking to get a list of OLVM developers that can join the peering program in October 2021 but nobody reached out so far. - I don't remember I have seen any reply from Alma so far. - Tried to reach out to oVirt China http://www.cnovirt.com/ as they seems to ship a rebuild of oVirt targeting Chinese speaking users without any success That said, no : oVirt is not dead. oVirt 4.5 is being developed actively and it has 566 bugzilla tickets targeting it: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt... and 242 of them have been already handled.

Le 5 févr. 2022 11:31, Thomas Hoberg a écrit :

Please have a look here: https://access.redhat.com/support/policy/updates/rhev/

Without a commercial product to pay the vast majority of the developers, there is just no chance oVirt can survive (unless you're ready to take over). RHV 4.4 full support ends this August and that very likely means that oVirt won't receive updates past July (judging by how things happened with 4.3).

And those will be CI tested against the Stream Beta not EL8 including RHEL.

Only with a RHV support contract ($) you will receive service until 2024 and with extended support ($$$) until 2026.

oVirt is dead already. They have known since October. They should have told us last year. _______________________________________________ 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/ZPQ7DO75CVINFK... _______________________________________________ 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/DDYD27NS5QB5LI...

-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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.*

Il giorno lun 7 feb 2022 alle ore 09:28 Thomas Hoberg <thomas@hoberg.net> ha scritto:

Sandro, I am ever so glad you're fighting on, buon coraggio!

Thanks :-)

Yes, please write a blog post on how oVirt could develop without a commercial downstream product that pays your salaries.

I have no magic recipe but I know oVirt is used in several universities with computer science departments. If just 1 student for each of them would contribute 1 patch per semester that would help keeping oVirt alive even without any downstream company backing it. And there are also people in this list like @Jean-Louis Dupond <jean-louis@dupond.be> who are contributing fixes, latest is here https://github.com/oVirt/ovirt-engine/pull/59 . I don't want to write a book on how an opensource project can be healthy, I believe there are already out there :-) . It would indeed help if some company or foundation would show up and get engaged with the project but this is not strictly needed for an open source project to be alive.

Ideally you'd add a perspective for current HCI users, many of which chose this approach, because a fault-tolerant SAN or NAS wasn't available.

I'll let the storage team to answer here

And since most of us here will probably agree that PaaS is the future, another post or a section on how a transition to OKD and KubeVirt could be done for current oVirt users, would be great, too.

I'll work on this one for OKD Virtualization SIG. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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.*

To replicate HCI without Gluster, is there a way to set up a Managed Block Storage (I think that means Ceph?) cluster hosted on the hypervisors, in a similar way as a Gluster Replica 3 ? Is that possible/recommended or discouraged? We are not ready for Openshift/Kubevirt yet and we would like to investigate whether oVirt on Ceph in HCI is doable. Thank for any feedback Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group On Mon, Feb 7, 2022 at 10:47 PM Nir Soffer <nsoffer@redhat.com> wrote:

On Mon, Feb 7, 2022 at 3:04 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

...

Il giorno lun 7 feb 2022 alle ore 09:28 Thomas Hoberg <thomas@hoberg.net> ha scritto:

...

Sandro, I am ever so glad you're fighting on, buon coraggio!

Thanks :-)

...

Yes, please write a blog post on how oVirt could develop without a commercial downstream product that pays your salaries.

I have no magic recipe but I know oVirt is used in several universities with computer science departments. If just 1 student for each of them would contribute 1 patch per semester that would help keeping oVirt alive even without any downstream company backing it. And there are also people in this list like @Jean-Louis Dupond <jean-louis@dupond.be> who are contributing fixes, latest is here https://github.com/oVirt/ovirt-engine/pull/59 . I don't want to write a book on how an opensource project can be healthy, I believe there are already out there :-) . It would indeed help if some company or foundation would show up and get engaged with the project but this is not strictly needed for an open source project to be alive.

...

Ideally you'd add a perspective for current HCI users, many of which chose this approach, because a fault-tolerant SAN or NAS wasn't available.

I'll let the storage team to answer here

The oVirt storage team never worked on HCI and we don't plan to work on it in the future. HCI was designed and maintained by Gluster folks. Our contribution for HCI was adding 4k support, enabling usage of VDO.

Improving on the HCI side is unlikely to come from Red Hat, but nothing blocks other companies or contributors from working on this.

Our focus for 4.5 is Managed Block Storage and incremental backup.

Nir _______________________________________________ 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/5JBTH3JKW23ZRK...

-- 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>

On Mon, Feb 7, 2022 at 3:04 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:

The oVirt storage team never worked on HCI and we don't plan to work on it in the future. HCI was designed and maintained by Gluster folks. Our contribution for HCI was adding 4k support, enabling usage of VDO.

Improving on the HCI side is unlikely to come from Red Hat, but nothing blocks other companies or contributors from working on this.

Our focus for 4.5 is Managed Block Storage and incremental backup.

Nir

Hi Nir, thank you for the clear message and the confirmation of a suspicion that has been growing for a while: HCI is an unwanted stepchild, not an equally supported option or even a strategic direction. And it's perhaps not the only one: in the mean-time I can see VDO and the GUIs getting neglected, too. My problem (and that of potentially many others) is that this unbalanced attention wasn't communicated or made visible. HCI may have disappeared from the oVirt front page today, in fact it's hard to find these days, but it was very prominent on 4.3 when I started. And as a core developer you may not realize this, but the primary first exposure to oVirt by many (most?) newcomers isn't the command line. It's the Cockpit wizard, where there are two HCI choices next to the one SAN/NAS option where evidently 95% of the oVirt teams work went, which doesn't use Gluster, HCI, VDO or any of the GUIs. I was extremely naive to believe you'd only need to click buttons in GUIs to run a 3 node HCI VDO cluster, but actually that expectation came from the presentation on this site. And personally I believe that if that had worked, RHV-HCI would be thriving. But as it turned out, both the setup GUI and the operational GUI rarely ever worked, very likely because both were done by yet another team, while you guys only worked and tested at the Ansible level and with SAN/NAS storage. You will say that oVirt is a community project. I will say that if you advertise oVirt as "designed to manage your entire enterprise infrastructure" and put buttons in GUIs, people will take that at face value and expect them to work. I don't know how many oVirt-HCI deployments I did over the years, but for every release I've tried since 4.3.5 or so with the Cockpit HCI wizard, none has ever just worked. I've had to dig through logfiles all over the place to fix things like blacklisted storage, when I was using Gluster. Then there were VDO options that weren't supported yet on EL7 in 4.3 ansible scripts, VDO disappearing altogether after a kernel upgrade on EL8, Python 2/3 issues and I don't know how many other problems, just to get things set up. I just did a full fresh set of setups with oVirt 4.4.10 when I was testing the compatibility of the various downstream EL8 derivatives and it's still the same: the Cockpit setup HCI wizard never just works. By now I know where to fiddle, but it saps confidence in the product when every release fails the basic setup. I can hear you saying "our CI only tests at script level", can you guess why that has an impact on quality? And it was the same for nearly half of the operations in the oVirt GUI. I went through each and every one of them and for startes I often couldn't find out what they were supposed to do, while some even looked downright dangerous to click (e.g. "reset brick"). Export and import OVA were pure nightmares, because it turned out that the exported machines might in fact contain 100GB of zeros instead of the disk image. Even once that was fixed, interoperability with other hypervisors (that's the purpose of OVA), was zero. As explanation I was told here that OVA in-/export wasn't really "meant to be used", much like HCI I guess. There is a cluster upgrade button, but I think I only ever hit it once, only to notice that it just created more damage and didn't add convenience. In fact upgrading any node became an entirely manual job in the end, because it never worked. The gluster daemon never started properly after a reboot and resulted in ovirt-ha-broker, ovirt-ha-agent and vdsmd sulking, requiring carefully timed restarts to get going again. And then an upgrade procedure for a high-availability HCI from EL7/oVirt 4.3 to EL8/oVirt 4.4 that had 40 steps or so, none of which were allowed to fail and with no obvious failback just isn't "enterprise". To my eyes the value proposition of oVirt was "instant on-premise fault tolerant cloud", something I could then use to run VMs or indeed OpenShift on. oVirt never delivered in an enterprise quality and I can't see it getting any closer without a downstream product. Even a community needs a concrete vision, or perhaps at least a few real use cases.

Il giorno mer 9 feb 2022 alle ore 16:39 赵井达 <zhao_jda@massclouds.com> ha scritto:

Hi, I am the head of the oVirt China User Community, which is founded and maintained by a non-profit organization. Our site: www.cnovirt.com.

Hi, a huge welcome to the user mailing list!

First of all, thanks to the oVirt community for providing such an excellent open source project. We hope this project can continue forever.Our community currently has 1000+ registered users and an online communication group of 500+ enthusiasts.

The work we have done so far: 1. Share the oVirt tutorial in Chinese. 2. Answer the questions in the use of oVirt. (Due to language problems, these users cannot directly participate in the maillist) 3. The oVirt mirror site has been established: http://mirror.massclouds.com/ovirt/, which is convenient for users in China to obtain and update software packages. 4. Publish and maintain oVirt desktop client software opencc, https://github.com/cnovirt/opencc-ovirt-pro, https://gitee.com/cnovirt/opencc-ovirt-pro. 5. Publish and maintain the offline version, merge the engine rpm into the node and remove the dependency on the external network during deployment. An iso image of the engine is made to facilitate independent deployment.

We plan to contribute to the community in the following ways: 1. Collect user questions and feedback bugs to the community. 2. Try to participate in bug fixes. 3. Submit some code, such as oVirt's support for arm architecture and loongarch. 4. Participate in the preparation of Chinese version documents.

Looking forward to collaborating with the Chinese community! +Avital Pinnick <apinnick@redhat.com> a heads up we need to organize the docs to be able to accept contributions in different languages if not already able to accept contributions in that direction.

-- Jingda Zhao

发件人："Sandro Bonazzola" <sbonazzo@redhat.com> 发送日期：2022-02-07 15:54:30 收件人："Nathanaël Blanchet" <blanchet@abes.fr>,"Sanja Bonic" < sbonic@redhat.com> 抄送人："Thomas Hoberg" <thomas@hoberg.net>,"oVirt Users" <users@ovirt.org> 主题：[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page?

Il giorno sab 5 feb 2022 alle ore 13:30 Nathanaël Blanchet < blanchet@abes.fr> ha scritto:

...

Can anybody from redhat confirm what is supposed here, all my staff depends on the future of ovirt. How can we help to maintain this project alive if redhat dev are not implicated anymore? I may donate some hardware or is it unuseful?

Looks like this is being asked on several channels so I guess I'll end up writing a blog post or add some statement on the oVirt home page. Anyway, let me reiterate the message:

This has been discussed publicly ( https://lists.ovirt.org/archives/list/users@ovirt.org/message/VIYHOW3WDR6N4A... ) As a product, Redhat Virtualization has a different lifecycle than oVirt which is a community project. What will be the future of oVirt project depends on how the community will be shaping it. As members of the Red Hat team working on the oVirt project we are actively doing whatever we can to ensure that the project will survive after we'll stop working on it in the future. - We are moving the development to public platform (GitHub) - We are changing our release process to ship oVirt builds via widely supported community systems like Fedora COPR and CentOS CBS. - We started a peering program helping whoever would like to start having an active role in oVirt community trying to make the onboarding as easy as possible ( https://lists.ovirt.org/archives/list/users@ovirt.org/message/QQVZHTFBF7NVI6... ) - We actively reached out to Rocky Linux, Alma Linux and Oracle, trying to engage them (CentOS is already engaged providing Community Build System for Virtualization SIG). So, what will be the future of the oVirt project depends on how the community will be shaping it. You're welcome to contribute to shaping this future! https://ovirt.org/develop/

Up to now: - We have one person who reached out being interested to the peering program, Maithreyi Gopal ( https://lists.ovirt.org/archives/list/devel@ovirt.org/message/TSSE7U36UQTEGE... ) and she's been peered with @Sanja Bonic <sbonic@redhat.com> . - Rocky Linux replied they were discussing within the Foundation meeting about oVirt but I didn't got the result of the discussion yet. - Oracle replied they are looking to get a list of OLVM developers that can join the peering program in October 2021 but nobody reached out so far. - I don't remember I have seen any reply from Alma so far. - Tried to reach out to oVirt China http://www.cnovirt.com/ as they seems to ship a rebuild of oVirt targeting Chinese speaking users without any success

That said, no : oVirt is not dead. oVirt 4.5 is being developed actively and it has 566 bugzilla tickets targeting it: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt... and 242 of them have been already handled.

...

Le 5 févr. 2022 11:31, Thomas Hoberg a écrit :

Please have a look here: https://access.redhat.com/support/policy/updates/rhev/

Without a commercial product to pay the vast majority of the developers, there is just no chance oVirt can survive (unless you're ready to take over). RHV 4.4 full support ends this August and that very likely means that oVirt won't receive updates past July (judging by how things happened with 4.3).

And those will be CI tested against the Stream Beta not EL8 including RHEL.

Only with a RHV support contract ($) you will receive service until 2024 and with extended support ($$$) until 2026.

oVirt is dead already. They have known since October. They should have told us last year. _______________________________________________ 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/ZPQ7DO75CVINFK... _______________________________________________ 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/DDYD27NS5QB5LI...

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA <https://www.redhat.com/>

sbonazzo@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.*

_______________________________________________ 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/PNYE27QDRA64HJ...

-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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.*

I've not been part of the ovirt project for 9 years now and have left red hat in 2018, so this isn't insider talk, just pure speculation. However... KubeVirt has been making a splash in the current height-of-fashion platform kubernetes and by extension in openshift. To me it only makes a lot of sense for red hat to converge their efforts on a single platform to rule them all. It's a learning curve, true, but what isn't? try Add to that the fact that nice technologies like mayastor are being developed for k8s, and you might start getting a bit of a light at the end of the tunnel, which just might not turn out to be an oncoming train. In short, give it a try, worst case - you end up on proxmox. On Sat, 5 Feb 2022, 22:28 Sketch, <ovirt@rednsx.org> wrote:

Interesting, I hadn't read about the planned migration from RHV to OpenShift. Based on what I've read here, it seems like 4.5 development is well underway, so I doubt 4.4 will be the last release of oVirt. That would mean August is probably not the end of the line.

However, the removal of gluster appears to be slated for 4.5, so it's possible it's intended as a final release to harmonize the feature between RHV and OpenShift somewhat, to make migration to OpenShift easier?

On Sat, 5 Feb 2022, Thomas Hoberg wrote:

...

Please have a look here: https://access.redhat.com/support/policy/updates/rhev/

Without a commercial product to pay the vast majority of the developers, there is just no chance oVirt can survive (unless you're ready to take over). RHV 4.4 full support ends this August and that very likely means that oVirt won't receive updates past July (judging by how things happened with 4.3).

And those will be CI tested against the Stream Beta not EL8 including RHEL.

Only with a RHV support contract ($) you will receive service until 2024 and with extended support ($$$) until 2026.

oVirt is dead already. They have known since October. They should have told us last year. _______________________________________________ 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/ZPQ7DO75CVINFK...

---

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/Q73NUBJZYMIWCJ...

I just hit across the fact that XOSAN (the "native" HCI solution for XCP-ng) is in fact LinStor... That's what's behind the €6000/year support fee, but there is a beta that's community and that I'll try fow now.

Alas, Ceph seems to take up an entire brain and mine regularly overflows just looking at their home page.

True, but with Highly Available NFS on the oVirt Nodes (Hyperconverged) ... It's just hard to setup, you need pacemaker and DRBD. Best Regards,Strahil Nikolov On Sun, Feb 6, 2022 at 23:07, gary@ravnalaska.net<gary@ravnalaska.net> wrote: I have been using NFS and iSCSI for a couple of years now and they work so much better for me than GlusterFS ever did. Gary On 2022-02-04 06:05, Thomas Hoberg wrote:

I just read this message: https://bugzilla.redhat.com/show_bug.cgi?id=2016359

I am shocked but not surprised. And very, very sad.

But I believe this decision needs to be communicated more prominently, as people should not get aboard a project already axed. _______________________________________________ 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/RMWAAOUJXYPGWC...

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/YK4AHNSEY2J264...