Hi Thomas,

> On 1. 4. 2021, at 23:44, Thomas Hoberg <tho...@hoberg.net> wrote:
> 
> I personally consider the fact that you gave up on 4.3/CentOS7 before CentOS 
> 8 could have even been remotely reliable to run "a free open-source 
> virtualization solution for your entire enterprise", a rather violent break 
> of trust.

it wasn’t really any different from past big releases. It’s been in development 
for roughly a year. Sure, there were hiccups during el7->el8 transition, but it 
didn’t seem to me any worse than when we moved from el6 to el7.

> 
> I understand Redhat's motivation with Python 2/3 etc., but users just don't. 
> Please just try for a minute to view this from a user's perspective.

it’s not RedHat’s motivation, it’s python 2 end of life that was on January 
2020 already. Every larger project written in python suffered, we already 
exceeded py2 EOL by several months but it couldn’t have been avoided. 
Users may not care, but there’s no way for developers to work around a language 
deprecation/redesign. I do not see how we could do anything about it.

> With CentOS 7 supported until 2024, we naturally expect the added value on 
> top via oVirt to persist just as long.

oVirt has nothing to do with CentOS, it’s just been our choice to build on as a 
stable and ubiquitous OS to build on, but it doesn’t define our own lifecycle.

> 
> And with CentOS 8 support lasting until the end of this year, oVirt 4.4 can't 
> be considered "Petrus" or a rock to build on.

right, the end of good old CentOS model is a big issue we have to sort out 
before the end of the year. There’s been previous threads on this topic, we do 
have CentOS Stream support for development, for stable user environment we will 
probably need something else. Things are in motion, there’s “free” RHEL 
offering, there are multiple other clones like Rocky or Alma, patches on the 
way to support them.

> 
> Most of us run oVirt simply because we are most interested in the VMs it runs 
> (tenants paying rent).
> 
> We're not interested in keeping oVirt itself stable and from failing after 
> any update to the house of cards.
> 
> And yes, by now I am sorry to have chosen oVirt at all, finding that 4.3 was 
> abandonend before 4.4 or the CentOS 8 below was even stable and long before 
> the base OS ran out of support.

I’m sorry for your experience. 
It’s understandable end users do not see the developer’s issues. But this is an 
open source project, some involvement is kind of expected. if you’re looking 
for a guaranteed support without dealing with “details” you can always consider 
commercial offering, be it RHV or VMware or whatever else.

Maintaining older versions is usually “the thing” that you get with commercial 
products. OSS projects usually offer backward compatibility only to a certain 
degree depending of available resources. We don’t really have them, we cannot 
maintain python2, we cannot maintain CentOS 7 or keep running CentOS 8 program. 
If there is anyone interested in help, provide automation for older versions, 
keep fixing it, add other operating system support and maintain it, then 
absolutely, please come forward and let’s do that by all means.

Thanks,
michal

> 
> To the users out there oVirt is a platform, a tool, not a means to itself.
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/JHSFTNGNOMYNCE4H2CF55DXIXGMCASMK/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3PG4LNW5Z4EEV3YW2YQ37UBOX7USW5G4/

Reply via email to