Hmm. So if Gluster is being deprecated, what is it being replaced with? Also, Nir did ask if this also applies to ovirt -- would be interesting to see the response to that question. -derek On Fri, February 4, 2022 10:05 am, Thomas Hoberg wrote: -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

Maybe its a perfect time to add ( again ) Ceph into discution. Leo On Fri, Feb 4, 2022, 18:21 Thomas Hoberg <thomas(a)hoberg.net&gt; 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&lt;users(a)ovirt.org&gt; wrote: _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/SJXJV7442IV...

My idea is that Gluster is there and is in use and it should not be removed just because the downstream is closing to EOL. A simple warning on the website is enough. Best Regards, Strahil Nikolov В петък, 4 февруари 2022 г., 22:11:45 Гринуич+2, Dori Seliškar via Users <users(a)ovirt.org&gt; написа: 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... ) 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(a)ovirt.org&gt; wrote: _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/SJXJV7442IV... _______________________________________________Users mailing list -- users(a)ovirt.orgTo unsubscribe send an email to users-leave(a)ovirt.orgPrivacy Statement: https://www.ovirt.org/privacy-policy.htmloVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5IUFP5ZVJHJ... _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/WNXFPUTB6BG...

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? 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(a)ovirt.org To unsubscribe send an email to users-leave(a)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/ZPQ7DO75CVI...

Sandro, I am ever so glad you're fighting on, buon coraggio! Yes, please write a blog post on how oVirt could develop without a commercial downstream product that pays your salaries. 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. 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.

On Mon, Feb 7, 2022 at 3:04 PM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; 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

oVirt's MBS (CEPH) support is targeted for external CEPH clusters, I'm not aware of any effort to colocate the services like with gluster. With gluster we tried to ignore the impact of one affecting the other, with CEPH being more demanding it would be even more difficult. it might work in the ideal case, but since there is no awareness (like there is in Gluster) when you e.g. fence bunch of oVirt hosts you may easily do some damage to each. OKD Virtualization (okd+kubevirt/hco+rook) would be doable in future...most people are not ready just yet, and the project is not so polished yet either, but it will get there... Thanks, michal

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. 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. -- Jingda Zhao 发件人："Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; 发送日期：2022-02-07 15:54:30 收件人："Nathanaël Blanchet" <blanchet(a)abes.fr&gt;,&quot;Sanja Bonic" <sbonic(a)redhat.com&gt; 抄送人："Thomas Hoberg" <thomas(a)hoberg.net&gt;,&quot;oVirt Users" <users(a)ovirt.org&gt; 主题：[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(a)abes.fr&gt; 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/VIYHOW3WDR6... ) 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/QQVZHTFBF7N... ) - 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/TSSE7U36UQT... ) and she's been peered with @Sanja Bonic . - 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%3Aov... 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(a)ovirt.org To unsubscribe send an email to users-leave(a)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/ZPQ7DO75CVI... _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/DDYD27NS5QB... -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA sbonazzo(a)redhat.com | | | | Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

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(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/ZPQ7DO75CVI...

Il giorno ven 4 feb 2022 alle ore 20:28 Strahil Nikolov via Users < users(a)ovirt.org&gt; ha scritto: I wouldn't have been able to say this in a better way :-) -- 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.*

On Fri, 4 Feb 2022, Leo David wrote: Ceph already works pretty well in 4.4 in general. It would be nice if the hosted engine supported ceph directly, but you can currently use an iSCSI or NFS export from ceph to host it. Personally, I had issues migrating 4.3->4.4 on gluster, and ended up moving to a standalone engine for 4.4 instead. I had planned to migrate back to self-hosted later, but standalone is so much simpler and less trouble-prone, I'm not sure I want to go back to self-hosted.

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(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/RMWAAOUJXYP...

Il giorno ven 4 feb 2022 alle ore 16:06 Thomas Hoberg <thomas(a)hoberg.net&gt; ha scritto: This is being communicated for RHV and RHGS in their communication channels. As for oVirt and Gluster, there's no EOL announced The Hyperconverged guide for oVirt has been moved from the main documentation section to https://ovirt.org/dropped/gluster-hyperconverged/ as nobody is still maintaining it and it doesn't fit the rest of the content of the doc directory (docs are asciidoc, this guide is still markdown). Also, being Gluster storage deprecated for RHV I would expect testing in this area to be reduced by Red Hat QE but this doesn't mean that for oVIrt someone else can step in and provide the testing coverage for this storage type. The code for handling Gluster and Hyperconverged is not going to be removed as far as I know. -- 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.*