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.