On Friday, 30 July 2021 06:57:04 CEST tommy wrote: yes, it's not operating system version, but installed oVirt version on the host (but not oVirt engine, there's only one engine and host haven't engine installed). Could you please improve the doc [1]? Thanks Vojta [1] https://github.com/oVirt/ovirt-site/edit/master/source/documentation/ upgrade_guide/index.adoc

Hello Tommy, You can use github to report issues or edit the pages if you look at the bottom of https://www.ovirt.org/documentation/ Regards, Paul S. ________________________________ From: tommy <sz_cuitao(a)163.com&gt; Sent: 30 July 2021 08:51 To: 'Vojtech Juranek' <vjuranek(a)redhat.com>; 'users' <users(a)ovirt.org&gt; Subject: [ovirt-users] Re: About the cluster compatibility version Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. I still find a lot of errors in the document, but I don't know how to help? Can you tell me the steps to improve the documentation? I'd like to help in any way I can. -----Original Message----- From: Vojtech Juranek <vjuranek(a)redhat.com&gt; Sent: Friday, July 30, 2021 3:01 PM To: 'users' <users(a)ovirt.org&gt; Cc: tommy <sz_cuitao(a)163.com&gt; Subject: Re: [ovirt-users] About the cluster compatibility version On Friday, 30 July 2021 06:57:04 CEST tommy wrote: yes, it's not operating system version, but installed oVirt version on the host (but not oVirt engine, there's only one engine and host haven't engine installed). Could you please improve the doc [1]? Thanks Vojta [1] https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.... upgrade_guide/index.adoc _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o... To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

You have a point. I am increasingly aware of the importance of documentation, especially good documentation that clearly illustrates the history of development, which can help readers quickly get started with software systems. -----Original Message----- From: Vojtech Juranek <vjuranek(a)redhat.com&gt; Sent: Friday, July 30, 2021 4:21 PM To: tommy <sz_cuitao(a)163.com&gt; Cc: users(a)ovirt.org Subject: Re: [ovirt-users] About the cluster compatibility version On Friday, 30 July 2021 09:51:08 CEST you wrote: help? you need to find appropriate document, fix it and send a pull request. There's a README [1] with the step in oVirt site git repo [1] or if you want to send a pull request, you can find guide how to do it on [2]. Looking more into the original question you asked, it's maybe correct. I don't know if we have any strict rules when cluster version is bumped, but it seems in the past it was done mainly to ensure OS has specific features provided advanced virtualization packages, which are usually available only on specific OS version and higher. So in this case the documentation is correct (and I was wrong in my previous answer), as OS version determines packages available on the host and these determines capabilities of tools (like libvirt, qemu) which oVirt is build upon. Hopefully makes sense. [1] https://github.com/oVirt/ovirt-site/blob/master/README.md [2] https://docs.github.com/en/github/collaborating-with-pull-requests/ proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request