I upgraded. The upgrade seems to have been successful. However, the distribution OS of the self-hosted engine did not change. # cat /etc/system-release CentOS Linux release 8.3.2011 Do I need to manually change my self-hosted engine distribution to Stream 8? I saw this URL for the version upgrade procedure. https://www.ovirt.org/documentation/upgrade_guide/index.html#Updates_between...
I'm not sure if the hosted engine is on stream yet. I'm also on 4.4.6 and while my nodes are CentOS 8 stream my hosted engine is also still 8.3 On Mon, May 31, 2021 at 3:45 AM mail--- via Users <users@ovirt.org> wrote:
I upgraded. The upgrade seems to have been successful. However, the distribution OS of the self-hosted engine did not change.
# cat /etc/system-release CentOS Linux release 8.3.2011
Do I need to manually change my self-hosted engine distribution to Stream 8?
I saw this URL for the version upgrade procedure.
https://www.ovirt.org/documentation/upgrade_guide/index.html#Updates_between... _______________________________________________ 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/6SWPMUJEVDQVUZ...
On Mon, May 31, 2021 at 4:33 PM Jayme <jaymef@gmail.com> wrote:
I'm not sure if the hosted engine is on stream yet. I'm also on 4.4.6 and while my nodes are CentOS 8 stream my hosted engine is also still 8.3
On Mon, May 31, 2021 at 3:45 AM mail--- via Users <users@ovirt.org> wrote:
I upgraded. The upgrade seems to have been successful. However, the distribution OS of the self-hosted engine did not change.
# cat /etc/system-release CentOS Linux release 8.3.2011
Do I need to manually change my self-hosted engine distribution to Stream 8?
I saw this URL for the version upgrade procedure. https://www.ovirt.org/documentation/upgrade_guide/index.html#Updates_between...
I'd like to clarify the relation of oVirt and CentOS Stream: 1. In images that oVirt publishes and include an OS, this OS is now (since 4.4.6) CentOS Stream. For ovirt-node, this means that if you upgrade to 4.4.6 node, you get Stream. For ovirt-engine-appliance, once you install this (as part of a hosted-engine deployment), the VM you get is a plain OS installation that is not automatically upgraded. It's up to the user to upgrade, also to Stream if desirable/needed. 2. Everything else is plain old RPMs. oVirt tests these on Stream. If any other rebuild of Red Hat Enterprise Linux works for you, you are welcome to use that. As Sandro published today in the users survey results, some of us do. Best regards, -- Didi
Thank you. It became a stream from 4.4.6, but there is no official procedure to switch from stream to Alma or Rocky or anything else. So, if you have a fresh install from 4.4.6, can you assume that the engine distribution has no choice but Stream? # Excludes unofficial switching. So, if oVirt tests with streams, I think it's safer to switch to streams for environments upgraded from 4.4.5 or earlier. Are there any special operations to switch the engine appliance to the stream? Please let me know if there is a manual based on oVirt. Also, if there is a special operation, is it likely to be documented in the future?
On Tue, Jun 1, 2021 at 4:15 AM mail--- via Users <users@ovirt.org> wrote:
Thank you.
It became a stream from 4.4.6, but there is no official procedure to switch from stream to Alma or Rocky or anything else.
There is also no official procedure to switch an oVirt installation from CentOS Linux to CentOS Stream: For plain setups (and including the appliance) you are supposed to follow the official procedure of CentOS. The only thing specific to oVirt is when upgrading ovirt-node.
So, if you have a fresh install from 4.4.6, can you assume that the engine distribution has no choice but Stream?
No, that's not what I said. I suggest to simply read the 4.4.6 release notes: https://www.ovirt.org/release/4.4.6/ If you refer to a hosted-engine setup, then indeed the only way to install this using the provided ovirt-engine-appliance will get you Stream. But if you install standalone, you can try anything you want. If people want to deploy hosted-engine using something other than the ovirt-engine-appliance, the community is welcome to work on that. The oVirt project only uses Stream and builds/tests on Stream, but will accept patches to support any other OS.
# Excludes unofficial switching.
So, if oVirt tests with streams, I think it's safer to switch to streams for environments upgraded from 4.4.5 or earlier.
If in "safer" you mean in the broadest sense of the word, then I might agree - but I strongly recommend that people carefully study their options and make an informed decision. For some use cases, using Stream makes the most sense. For others, Alma/Rocky do. For yet others, Oracle Linux or Red Hat Enterprise Linux do. And, BTW, this is by no means an exhaustive list - you can find a larger list, even if likely still non-exhaustive, in wikipedia: https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux_derivatives
Are there any special operations to switch the engine appliance to the stream? Please let me know if there is a manual based on oVirt.
I am not aware of an official one. The official one from CentOS is quite short and simple, and IIRC was already partially copied in other relevant posts in this list. For ovirt-node, you should follow existing ovirt-node documentation - but see the release notes.
Also, if there is a special operation, is it likely to be documented in the future?
As far as the oVirt project is concerned, we'll most likely consider a future need for such a procedure to be a bug. Meaning, if following the official migration procedure of whatever other OS is broken due to oVirt-specific code, we'd like to get a bug report. Best regards, -- Didi
On Tue, Jun 1, 2021 at 4:15 AM mail--- via Users <users(a)ovirt.org> wrote:
There is also no official procedure to switch an oVirt installation from CentOS Linux to CentOS Stream: For plain setups (and including the appliance) you are supposed to follow the official procedure of CentOS. The only thing specific to oVirt is when upgrading ovirt-node.
Thank you, I understand.
No, that's not what I said. I suggest to simply read the 4.4.6 release notes:
I'm sorry if it's misleading. I am not an English speaking person. I just wanted to make sure that my thinking was right, and there is no nuance to blame you. However, thanks to the answers I received, I was able to understand once again that there is virtually no option other than "Stream" for self-hosted using appliance images.
If you refer to a hosted-engine setup, then indeed the only way to install this using the provided ovirt-engine-appliance will get you Stream.
But if you install standalone, you can try anything you want.
If people want to deploy hosted-engine using something other than the ovirt-engine-appliance, the community is welcome to work on that. The oVirt project only uses Stream and builds/tests on Stream, but will accept patches to support any other OS.
If in "safer" you mean in the broadest sense of the word, then I might agree - but I strongly recommend that people carefully study their options and make an informed decision.
For some use cases, using Stream makes the most sense. For others, Alma/Rocky do. For yet others, Oracle Linux or Red Hat Enterprise Linux do. And, BTW, this is by no means an exhaustive list - you can find a larger list, even if likely still non-exhaustive, in wikipedia:
https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux_derivatives
I am not aware of an official one. The official one from CentOS is quite short and simple, and IIRC was already partially copied in other relevant posts in this list.
For ovirt-node, you should follow existing ovirt-node documentation - but see the release notes.
As far as the oVirt project is concerned, we'll most likely consider a future need for such a procedure to be a bug. Meaning, if following the official migration procedure of whatever other OS is broken due to oVirt-specific code, we'd like to get a bug report.
Best regards,
I understood that basically I should follow the instructions of each distribution. If I run into a bug with a distro supported by oVirt, it's definitely a problem to report. It was very easy to understand.
participants (3)
-
Jayme -
mail＠chattytak.com -
Yedidyah Bar David