Il giorno ven 11 dic 2020 alle ore 16:22 Charles Kozler <
char...@fixflyer.com> ha scritto:

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

oVirt 4.4.3 Requires CentOS 8.2 or higher but without 8.3 and Advanced
Virtualization 8.3 you're going to have cluster level 4.5 not available.




>
>
>
>
> On Fri, Dec 11, 2020 at 10:08 AM Sandro Bonazzola <sbona...@redhat.com>
> wrote:
>
>>
>>
>> Il giorno ven 11 dic 2020 alle ore 15:49 Charles Kozler <
>> char...@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 <sbona...@redhat.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> Il giorno gio 10 dic 2020 alle ore 21:51 Charles Kozler <
>>>> char...@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-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/7IUWGES2IG4BELLUPMYGEKN3GC6XVCHA/
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sandro Bonazzola
>>>>
>>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>>>
>>>> Red Hat EMEA <https://www.redhat.com/>
>>>>
>>>> sbona...@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.*
>>>>
>>>>
>>>>
>>> *Notice to Recipient*: https://www.fixflyer.com/disclaimer
>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>
>> Red Hat EMEA <https://www.redhat.com/>
>>
>> sbona...@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.
>> <https://mojo.redhat.com/docs/DOC-1199578>*
>>
>>
>>
> *Notice to Recipient*: https://www.fixflyer.com/disclaimer



-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

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

sbona...@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.
<https://mojo.redhat.com/docs/DOC-1199578>*
_______________________________________________
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/6QSYZT7T6UXMPDWKLQT36SYBGTLGJM7Y/

Reply via email to