What goes in to oVirt goes in to RHV if I understand correctly, right? If so sorry, I meant upstream

If I am understanding how all of this is changing correctly then this move to stream will only serve to benefit oVirt as it speeds up the pace of CentOS in the ecosystem and therefore potentially won't have breaking changes dependent and waiting on RHEL to release so CentOS can be built

If I remember correctly (and I could be confusing this with another application), oVirt requires CentOS 7.3 or higher right?

On Fri, Dec 11, 2020 at 10:08 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il giorno ven 11 dic 2020 alle ore 15:49 Charles Kozler <charles@fixflyer.com> ha scritto:

CentOS was the downstream of RHEL but has now become the upstream

I guess oVirt was always downstream as well - yes?

No. oVirt is oVirt. It's  downstream to nothing.

And it used to work and being used on Fedora which is upstream to RHEL and to CentOS Stream.

Fedora moved just way too fast and we had to drop the effort trying to keep the pace: https://blogs.ovirt.org/2020/05/ovirt-and-fedora/

With CentOS Stream we are just moving the point when CentOS breaks oVirt. Instead to wait a couple of months after RHEL release (CentOS 8.3 just broke oVirt: we can't build oVirt Node and oVirt appliance anymore due to a bug in lorax package, it's preventing oVirt 4.4.4 to be released because advanced virtualization build is missing a dependency which is in RHEL but not in CentOS due to a bug in CentOS compose system) we'll have the fix in oVirt a month before RHEL will be released.

 

If so then yes, I can't see much changing in the ways of oVirt

As far as I can tell by looking at CentOS 8.3, it will change in something better.

 

On Fri, Dec 11, 2020 at 2:59 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il giorno gio 10 dic 2020 alle ore 21:51 Charles Kozler <charles@fixflyer.com> ha scritto:

I guess this is probably a question for all current open source projects that red hat runs but - 

Does this mean oVirt will effectively become a rolling release type situation as well?

There's no plan to make oVirt a rolling release.

 

How exactly is oVirt going to stay open source and stay in cadence with all the other updates happening around it on packages/etc that it depends on if the streams are rolling release? Do they now need to fork every piece of dependency?

We are going to test regularly oVirt on CentOS Stream, releasing oVirt Node and oVirt appliance after testing them, without any difference to what we are doing right now with CentOS Linux.

Any raised issue will be handled as usual.

What exactly does this mean for oVirt going forward and its overall stability?

oVirt plans about CentOS Stream have been communicated one year ago here: https://blogs.ovirt.org/2019/09/ovirt-and-centos-stream/

That said, please note that oVirt documentation mentions "Enterprise Linux" almost everywhere and not explicitly CentOS Linux.

As far as I can tell any RHEL binary compatible rebuild should just work with oVirt despite I would recommend to follow what will be done within oVirt Node and oVirt Appliance.

 

Notice to Recipient: https://www.fixflyer.com/disclaimer_______________________________________________
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/7IUWGES2IG4BELLUPMYGEKN3GC6XVCHA/

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

Notice to Recipient: https://www.fixflyer.com/disclaimer

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

Notice to Recipient: https://www.fixflyer.com/disclaimer