[ANN] oVirt 4.4.4 is now generally available
oVirt 4.4.4 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJN... ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.4 Release? This update is the fourth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - oVirt Node (based on CentOS Linux 8.3) - CentOS Stream (tech preview) oVirt Node and Appliance have been updated, including: - oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/ - Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9... - CentOS Linux 8 (2011): https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html - Advanced Virtualization 8.3 See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.4 release highlights: https://www.ovirt.org/release/4.4.4/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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.*
Hi Sandro, thanks for the release! Should this fix the upgrade problems to cluster version 4.5 too when using CentOS 8.3 + updates? Thanks, Gianluca On Mon, Dec 21, 2020 at 2:26 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade
Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported.
For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJN... ) Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. -
For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. -
For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. -
For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>.
What’s new in oVirt 4.4.4 Release?
This update is the fourth in a series of stabilization updates to the 4.4 series.
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.3 -
CentOS Linux (or similar) 8.3 -
CentOS Stream (tech preview)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:
-
Red Hat Enterprise Linux 8.3 -
CentOS Linux (or similar) 8.3 -
oVirt Node (based on CentOS Linux 8.3) -
CentOS Stream (tech preview)
oVirt Node and Appliance have been updated, including:
-
oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/ -
Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9...
-
CentOS Linux 8 (2011): https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html -
Advanced Virtualization 8.3
See the release notes [1] for installation instructions and a list of new features and bugs fixed.
Notes:
-
oVirt Appliance is already available for CentOS Linux 8 -
oVirt Node NG is already available for CentOS Linux 8
Additional resources:
-
Read more about the oVirt 4.4.4 release highlights: https://www.ovirt.org/release/4.4.4/ -
Get more oVirt project updates on Twitter: https://twitter.com/ovirt -
Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/
[1] https://www.ovirt.org/release/4.4.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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.*
_______________________________________________ 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/KMYD2GAHZXWLE4...
Il giorno lun 21 dic 2020 alle ore 14:31 Gianluca Cecchi < gianluca.cecchi@gmail.com> ha scritto:
Hi Sandro, thanks for the release!
Should this fix the upgrade problems to cluster version 4.5 too when using CentOS 8.3 + updates?
Yes
Thanks, Gianluca
On Mon, Dec 21, 2020 at 2:26 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade
Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported.
For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJN... ) Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. -
For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. -
For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. -
For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>.
What’s new in oVirt 4.4.4 Release?
This update is the fourth in a series of stabilization updates to the 4.4 series.
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.3 -
CentOS Linux (or similar) 8.3 -
CentOS Stream (tech preview)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:
-
Red Hat Enterprise Linux 8.3 -
CentOS Linux (or similar) 8.3 -
oVirt Node (based on CentOS Linux 8.3) -
CentOS Stream (tech preview)
oVirt Node and Appliance have been updated, including:
-
oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/ -
Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9...
-
CentOS Linux 8 (2011): https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html -
Advanced Virtualization 8.3
See the release notes [1] for installation instructions and a list of new features and bugs fixed.
Notes:
-
oVirt Appliance is already available for CentOS Linux 8 -
oVirt Node NG is already available for CentOS Linux 8
Additional resources:
-
Read more about the oVirt 4.4.4 release highlights: https://www.ovirt.org/release/4.4.4/ -
Get more oVirt project updates on Twitter: https://twitter.com/ovirt -
Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/
[1] https://www.ovirt.org/release/4.4.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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.*
_______________________________________________ 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/KMYD2GAHZXWLE4...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
On Mon, Dec 21, 2020 at 2:36 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno lun 21 dic 2020 alle ore 14:31 Gianluca Cecchi < gianluca.cecchi@gmail.com> ha scritto:
Hi Sandro, thanks for the release!
Should this fix the upgrade problems to cluster version 4.5 too when using CentOS 8.3 + updates?
Yes
Hi Sandro, I confirm that on a test cluster with 3 plain CentOS 8.3 hosts and an external CentOS 8.3 based engine I was able to update all of them to 4.4.4 and then update both cluster and DC level to 4.5. Can you recall, apart from being now at the latest level, what kind of new features I should expect in 4.5 vs 4.4 so that I can also test and use them for improvements (eg in storage domain version/features, incremental backup, snapshotting features, export and such...)? thanks Gianluca
Il giorno lun 21 dic 2020 alle ore 18:08 Gianluca Cecchi < gianluca.cecchi@gmail.com> ha scritto:
On Mon, Dec 21, 2020 at 2:36 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno lun 21 dic 2020 alle ore 14:31 Gianluca Cecchi < gianluca.cecchi@gmail.com> ha scritto:
Hi Sandro, thanks for the release!
Should this fix the upgrade problems to cluster version 4.5 too when using CentOS 8.3 + updates?
Yes
Hi Sandro, I confirm that on a test cluster with 3 plain CentOS 8.3 hosts and an external CentOS 8.3 based engine I was able to update all of them to 4.4.4 and then update both cluster and DC level to 4.5. Can you recall, apart from being now at the latest level, what kind of new features I should expect in 4.5 vs 4.4 so that I can also test and use them for improvements (eg in storage domain version/features, incremental backup, snapshotting features, export and such...)?
Cluster compatibility level has been introduced with: *Bug 1877675* <https://bugzilla.redhat.com/show_bug.cgi?id=1877675> - [RFE] Introduce Datacenter and cluster level 4.5 It tracks: *- Bug 1725166 <https://bugzilla.redhat.com/show_bug.cgi?id=1725166> - [RFE] Private VLAN / port isolation* *- Support for Intel Icelake Server Family * *- **Bug 1814565* <https://bugzilla.redhat.com/show_bug.cgi?id=1814565> - Report disk.usage for VMs with RHEL 8 guests - *Bug 1852718* <https://bugzilla.redhat.com/show_bug.cgi?id=1852718> - vGPU: VM failed to run with mdev_type instance - *Bug 1853194* <https://bugzilla.redhat.com/show_bug.cgi?id=1853194> - VM with disk on iscsi on environment with SELinux enforced fails to start on host - Exit message: Wake up from hibernation failed:internal error: child reported (status=125): unable to set security context - *Bug 1876605* <https://bugzilla.redhat.com/show_bug.cgi?id=1876605> - VM with scsi hostdev (scsi_generic custom property) fails on start:'node-name too long for qemu' +Martin Perina <mperina@redhat.com> , +Arik Hadas <ahadas@redhat.com> , +Tal Nisan <tnisan@redhat.com> , +Dominik Holler <dholler@redhat.com> feel free to add if I missed something. I think that having a page on oVirt documentation with features and requirements per supported cluster compatibility level would help. Gianluca, maybe you can open a bug for it?
thanks Gianluca
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
On Tue, Dec 22, 2020 at 11:03 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Cluster compatibility level has been introduced with: *Bug 1877675* <https://bugzilla.redhat.com/show_bug.cgi?id=1877675> - [RFE] Introduce Datacenter and cluster level 4.5
It tracks: *- Bug 1725166 <https://bugzilla.redhat.com/show_bug.cgi?id=1725166> - [RFE] Private VLAN / port isolation* *- Support for Intel Icelake Server Family * *- **Bug 1814565* <https://bugzilla.redhat.com/show_bug.cgi?id=1814565> - Report disk.usage for VMs with RHEL 8 guests - *Bug 1852718* <https://bugzilla.redhat.com/show_bug.cgi?id=1852718> - vGPU: VM failed to run with mdev_type instance - *Bug 1853194* <https://bugzilla.redhat.com/show_bug.cgi?id=1853194> - VM with disk on iscsi on environment with SELinux enforced fails to start on host - Exit message: Wake up from hibernation failed:internal error: child reported (status=125): unable to set security context - *Bug 1876605* <https://bugzilla.redhat.com/show_bug.cgi?id=1876605> - VM with scsi hostdev (scsi_generic custom property) fails on start:'node-name too long for qemu'
+Martin Perina <mperina@redhat.com> , +Arik Hadas <ahadas@redhat.com> , +Tal Nisan <tnisan@redhat.com> , +Dominik Holler <dholler@redhat.com> feel free to add if I missed something. I think that having a page on oVirt documentation with features and requirements per supported cluster compatibility level would help. Gianluca, maybe you can open a bug for it?
Done. It is here: https://bugzilla.redhat.com/show_bug.cgi?id=1910332 Gianluca
Il giorno lun 21 dic 2020 alle ore 15:57 Konstantin Shalygin <k0ste@k0ste.ru> ha scritto:
On 21.12.2020 16:22, Sandro Bonazzola wrote:
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
Sandro, is any plans to fix for OpenStack provider regressions for 4.4 release?
I see you opened two bugs about it: *Bug 1905113* <https://bugzilla.redhat.com/show_bug.cgi?id=1905113> - OpenStack Block Storage Provider (Cinder) regression: oVirt 4.4 Disk resize broken *Bug 1904669* <https://bugzilla.redhat.com/show_bug.cgi?id=1904669> - oVirt 4.3 -> 4.4 production upgrade: OpenStack Block Storage Provider (Cinder) regression Please consider most of the developers are going to be on vacation due to the upcoming holidays. I think storage team is looking into this but I see above bugs have not been targeted yet so a deeper investigation may be needed.
Thanks,
k
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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.*
Sandro, after my mention my two bugs was closed as deprecated feature of "old Cinder integration". But actually no one oVirt 4.4 doc mentioned about deprecations/cautions/warnings. How do you think, as manager of project, it's okay to just broke working code due loose tests and then deprecate it just by wave a hand?🤷♂️ Thanks, k Sent from my iPhone
On 21 Dec 2020, at 18:09, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno lun 21 dic 2020 alle ore 15:57 Konstantin Shalygin <k0ste@k0ste.ru> ha scritto: On 21.12.2020 16:22, Sandro Bonazzola wrote:
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020. Sandro, is any plans to fix for OpenStack provider regressions for 4.4 release?
I see you opened two bugs about it: Bug 1905113 - OpenStack Block Storage Provider (Cinder) regression: oVirt 4.4 Disk resize broken Bug 1904669 - oVirt 4.3 -> 4.4 production upgrade: OpenStack Block Storage Provider (Cinder) regression
Please consider most of the developers are going to be on vacation due to the upcoming holidays. I think storage team is looking into this but I see above bugs have not been targeted yet so a deeper investigation may be needed.
Thanks,
k
-- 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.
_______________________________________________ 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/GYAVGLTXHRGK27...
Il giorno lun 21 dic 2020 alle ore 18:33 Konstantin Shalygin <k0ste@k0ste.ru> ha scritto:
Sandro, after my mention my two bugs was closed as deprecated feature of "old Cinder integration". But actually no one oVirt 4.4 doc mentioned about deprecations/cautions/warnings.
Indeed, documentation is not aligned with +Eyal Shenitzky <eshenitz@redhat.com> 's comments on the bugs. A proper deprecation bug should have been opened and documentation should have been properly updated to clearly mark the feature as deprecated. Also the new implementation of cinderlib is not properly documented in oVirt Install Guide, I'll try to get it updated today.
How do you think, as manager of project, it's okay to just broke working code due loose tests and then deprecate it just by wave a hand?🤷♂️
I'll let storage team lead to reply to this specific question. I can only agree this has not been properly handled.
Thanks, k
Sent from my iPhone
On 21 Dec 2020, at 18:09, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno lun 21 dic 2020 alle ore 15:57 Konstantin Shalygin < k0ste@k0ste.ru> ha scritto:
On 21.12.2020 16:22, Sandro Bonazzola wrote:
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
Sandro, is any plans to fix for OpenStack provider regressions for 4.4 release?
I see you opened two bugs about it: *Bug 1905113* <https://bugzilla.redhat.com/show_bug.cgi?id=1905113> - OpenStack Block Storage Provider (Cinder) regression: oVirt 4.4 Disk resize broken *Bug 1904669* <https://bugzilla.redhat.com/show_bug.cgi?id=1904669> - oVirt 4.3 -> 4.4 production upgrade: OpenStack Block Storage Provider (Cinder) regression
Please consider most of the developers are going to be on vacation due to the upcoming holidays. I think storage team is looking into this but I see above bugs have not been targeted yet so a deeper investigation may be needed.
Thanks,
k
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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.*
_______________________________________________ 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/GYAVGLTXHRGK27...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
Il giorno mar 22 dic 2020 alle ore 10:01 Sandro Bonazzola < sbonazzo@redhat.com> ha scritto:
Il giorno lun 21 dic 2020 alle ore 18:33 Konstantin Shalygin < k0ste@k0ste.ru> ha scritto:
Sandro, after my mention my two bugs was closed as deprecated feature of "old Cinder integration". But actually no one oVirt 4.4 doc mentioned about deprecations/cautions/warnings.
Indeed, documentation is not aligned with +Eyal Shenitzky <eshenitz@redhat.com> 's comments on the bugs. A proper deprecation bug should have been opened and documentation should have been properly updated to clearly mark the feature as deprecated. Also the new implementation of cinderlib is not properly documented in oVirt Install Guide, I'll try to get it updated today.
+Eyal Shenitzky <eshenitz@redhat.com> , +Steve Goodman <sgoodman@redhat.com> , +Stefano Stagnaro <sstagnar@redhat.com> can you please review https://github.com/oVirt/ovirt-site/pull/2409 ?
How do you think, as manager of project, it's okay to just broke working code due loose tests and then deprecate it just by wave a hand?🤷♂️
I'll let storage team lead to reply to this specific question. I can only agree this has not been properly handled.
Thanks, k
Sent from my iPhone
On 21 Dec 2020, at 18:09, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno lun 21 dic 2020 alle ore 15:57 Konstantin Shalygin < k0ste@k0ste.ru> ha scritto:
On 21.12.2020 16:22, Sandro Bonazzola wrote:
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
Sandro, is any plans to fix for OpenStack provider regressions for 4.4 release?
I see you opened two bugs about it: *Bug 1905113* <https://bugzilla.redhat.com/show_bug.cgi?id=1905113> - OpenStack Block Storage Provider (Cinder) regression: oVirt 4.4 Disk resize broken *Bug 1904669* <https://bugzilla.redhat.com/show_bug.cgi?id=1904669> - oVirt 4.3 -> 4.4 production upgrade: OpenStack Block Storage Provider (Cinder) regression
Please consider most of the developers are going to be on vacation due to the upcoming holidays. I think storage team is looking into this but I see above bugs have not been targeted yet so a deeper investigation may be needed.
Thanks,
k
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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.*
_______________________________________________ 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/GYAVGLTXHRGK27...
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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>*
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
+Shir Fishbain <sfishbai@redhat.com> +Benny Zlotnik <bzlotnik@redhat.com>, Can you please review the manual and validate that all steps are up-to-date? On Tue, 22 Dec 2020 at 11:16, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mar 22 dic 2020 alle ore 10:01 Sandro Bonazzola < sbonazzo@redhat.com> ha scritto:
Il giorno lun 21 dic 2020 alle ore 18:33 Konstantin Shalygin < k0ste@k0ste.ru> ha scritto:
Sandro, after my mention my two bugs was closed as deprecated feature of "old Cinder integration". But actually no one oVirt 4.4 doc mentioned about deprecations/cautions/warnings.
Indeed, documentation is not aligned with +Eyal Shenitzky <eshenitz@redhat.com> 's comments on the bugs. A proper deprecation bug should have been opened and documentation should have been properly updated to clearly mark the feature as deprecated. Also the new implementation of cinderlib is not properly documented in oVirt Install Guide, I'll try to get it updated today.
+Eyal Shenitzky <eshenitz@redhat.com> , +Steve Goodman <sgoodman@redhat.com> , +Stefano Stagnaro <sstagnar@redhat.com> can you please review https://github.com/oVirt/ovirt-site/pull/2409 ?
How do you think, as manager of project, it's okay to just broke working code due loose tests and then deprecate it just by wave a hand?🤷♂️
I'll let storage team lead to reply to this specific question. I can only agree this has not been properly handled.
Thanks, k
Sent from my iPhone
On 21 Dec 2020, at 18:09, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno lun 21 dic 2020 alle ore 15:57 Konstantin Shalygin < k0ste@k0ste.ru> ha scritto:
On 21.12.2020 16:22, Sandro Bonazzola wrote:
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
Sandro, is any plans to fix for OpenStack provider regressions for 4.4 release?
I see you opened two bugs about it: *Bug 1905113* <https://bugzilla.redhat.com/show_bug.cgi?id=1905113> - OpenStack Block Storage Provider (Cinder) regression: oVirt 4.4 Disk resize broken *Bug 1904669* <https://bugzilla.redhat.com/show_bug.cgi?id=1904669> - oVirt 4.3 -> 4.4 production upgrade: OpenStack Block Storage Provider (Cinder) regression
Please consider most of the developers are going to be on vacation due to the upcoming holidays. I think storage team is looking into this but I see above bugs have not been targeted yet so a deeper investigation may be needed.
Thanks,
k
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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.*
_______________________________________________ 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/GYAVGLTXHRGK27...
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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>*
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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>*
-- Regards, Eyal Shenitzky
Sandro, FYI we are not against cinderlib integration, more than we are upgrade 4.3 to 4.4 due movement to cinderlib. But (!) current Managed Storage Block realization support only krbd (kernel RBD) driver - it's also not a option, because kernel client is always lagging behind librbd, and every update\bugfix we should *reboot whole host* instead simple migration of all VMs and then migrate it back. Also with krbd host will be use kernel page cache, and will not be unmounted if VM will crash (qemu with librbd is one userland process). So for me current situation look like this: 1. We update deprecated OpenStack code? Why, Its for delete?.. Nevermind, just update this code... 2. Hmm... auth tests doesn't work, to pass test just disable any OpenStack project_id related things... and... Done... 3. I don't care how current cinder + qemu code works, just write new one for linux kernel, it's optimal to use userland apps, just add wrappers (no, it's not); 4. Current Cinder integration require zero configuration on oVirt hosts. It's lazy, why oVirt administrator do nothing? just write manual how-to install packages - oVirt administrators love anything except "reinstall" from engine (no, it's not); 5. We broke old code. New features is "Cinderlib is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production". 6. Oh, we broke old code. Let's deprecate them and close PRODUCTION issues (we didn't see anything). And again, we are not hate new cinderlib integration. We just want that new technology don't break all PRODUCTION clustes. Almost two years ago I write on this issue https://bugzilla.redhat.com/show_bug.cgi?id=1539837#c6 about "before deprecate, let's help to migrate". For now I see that oVirt totally will disable QEMU RBD support and want to use kernel RBD module + python os-brick + userland mappers + shell wrappers. Thanks, I hope I am writing this for a reason and it will help build bridges between the community and the developers. We have been with oVirt for almost 10 years and now it is a crossroads towards a different virtualization manager. k So I see only regressions for now, hope we'll found some code owner who can catch this oVirt 4.4 only bugs. On 22.12.2020 12:01, Sandro Bonazzola wrote:
Il giorno lun 21 dic 2020 alle ore 18:33 Konstantin Shalygin <k0ste@k0ste.ru <mailto:k0ste@k0ste.ru>> ha scritto:
Sandro, after my mention my two bugs was closed as deprecated feature of "old Cinder integration". But actually no one oVirt 4.4 doc mentioned about deprecations/cautions/warnings.
Indeed, documentation is not aligned with +Eyal Shenitzky <mailto:eshenitz@redhat.com> 's comments on the bugs. A proper deprecation bug should have been opened and documentation should have been properly updated to clearly mark the feature as deprecated. Also the new implementation of cinderlib is not properly documented in oVirt Install Guide, I'll try to get it updated today.
How do you think, as manager of project, it's okay to just broke working code due loose tests and then deprecate it just by wave a hand?🤷♂️
I'll let storage team lead to reply to this specific question. I can only agree this has not been properly handled.
I just want to state that we are in the same situation like Konstantin, running a big cluster with Cinder storage (564 disks). This has worked perfectly for us in the past. I didn't upgrade to 4.4 yet, but reading now about Cinder deprecation makes me very sad. Why did you address bugs like https://bugzilla.redhat.com/show_bug.cgi?id=1743716 and then suddenly stop working on this? I know that Open Stack block storage (Cinder) always had Technology Preview status in oVirt so complaining about breaking "production" clusters might be futile from a "legal" point of view, but I want to confirm once again that is has been successfully used in large scale. Are there ways to lobby for keeping Cinder support in oVirt 4.4? Would it be possible to sponsor this feature? I know about and already tested cinderlib and I'm not unwilling to use it (like Konstantin). My objections at the present time are the same as Konstantin's and I'm at least expecting proper documentation (which is on it's way) and ideally a migration guide. Anyway, thanks a lot for great work so far. I hope I will remain a happy user. Matthias Am 22.12.20 um 17:31 schrieb Konstantin Shalygin:
Sandro, FYI we are not against cinderlib integration, more than we are upgrade 4.3 to 4.4 due movement to cinderlib.
But (!) current Managed Storage Block realization support only krbd (kernel RBD) driver - it's also not a option, because kernel client is always lagging behind librbd, and every update\bugfix we should *reboot whole host* instead simple migration of all VMs and then migrate it back. Also with krbd host will be use kernel page cache, and will not be unmounted if VM will crash (qemu with librbd is one userland process).
So for me current situation look like this:
1. We update deprecated OpenStack code? Why, Its for delete?.. Nevermind, just update this code...
2. Hmm... auth tests doesn't work, to pass test just disable any OpenStack project_id related things... and... Done...
3. I don't care how current cinder + qemu code works, just write new one for linux kernel, it's optimal to use userland apps, just add wrappers (no, it's not);
4. Current Cinder integration require zero configuration on oVirt hosts. It's lazy, why oVirt administrator do nothing? just write manual how-to install packages - oVirt administrators love anything except "reinstall" from engine (no, it's not);
5. We broke old code. New features is "Cinderlib is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production".
6. Oh, we broke old code. Let's deprecate them and close PRODUCTION issues (we didn't see anything).
And again, we are not hate new cinderlib integration. We just want that new technology don't break all PRODUCTION clustes. Almost two years ago I write on this issue https://bugzilla.redhat.com/show_bug.cgi?id=1539837#c6 about "before deprecate, let's help to migrate". For now I see that oVirt totally will disable QEMU RBD support and want to use kernel RBD module + python os-brick + userland mappers + shell wrappers.
Thanks, I hope I am writing this for a reason and it will help build bridges between the community and the developers. We have been with oVirt for almost 10 years and now it is a crossroads towards a different virtualization manager.
k
So I see only regressions for now, hope we'll found some code owner who can catch this oVirt 4.4 only bugs.
On 22.12.2020 12:01, Sandro Bonazzola wrote:
Il giorno lun 21 dic 2020 alle ore 18:33 Konstantin Shalygin <k0ste@k0ste.ru <mailto:k0ste@k0ste.ru>> ha scritto:
Sandro, after my mention my two bugs was closed as deprecated feature of "old Cinder integration". But actually no one oVirt 4.4 doc mentioned about deprecations/cautions/warnings.
Indeed, documentation is not aligned with +Eyal Shenitzky <mailto:eshenitz@redhat.com> 's comments on the bugs. A proper deprecation bug should have been opened and documentation should have been properly updated to clearly mark the feature as deprecated. Also the new implementation of cinderlib is not properly documented in oVirt Install Guide, I'll try to get it updated today.
How do you think, as manager of project, it's okay to just broke working code due loose tests and then deprecate it just by wave a hand?🤷♂️
I'll let storage team lead to reply to this specific question. I can only agree this has not been properly handled.
_______________________________________________ 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/ULTVTH5CLQPGFA...
-- Matthias Leopold IT Systems & Communications Medizinische Universität Wien Spitalgasse 23 / BT 88 /Ebene 00 A-1090 Wien Tel: +43 1 40160-21241 Fax: +43 1 40160-921200
On Tue, Dec 22, 2020 at 6:33 PM Konstantin Shalygin <k0ste@k0ste.ru> wrote:
Sandro, FYI we are not against cinderlib integration, more than we are upgrade 4.3 to 4.4 due movement to cinderlib.
But (!) current Managed Storage Block realization support only krbd (kernel RBD) driver - it's also not a option, because kernel client is always lagging behind librbd, and every update\bugfix we should reboot whole host instead simple migration of all VMs and then migrate it back. Also with krbd host will be use kernel page cache, and will not be unmounted if VM will crash (qemu with librbd is one userland process).
There was rbd-nbd support at some point in cinderlib[1] which addresses your concerns, but it was removed because of some issues +Gorka, are there any plans to pick it up again? [1] https://github.com/Akrog/cinderlib/commit/a09a7e12fe685d747ed390a59cd42d0acd...
So for me current situation look like this:
1. We update deprecated OpenStack code? Why, Its for delete?.. Nevermind, just update this code...
2. Hmm... auth tests doesn't work, to pass test just disable any OpenStack project_id related things... and... Done...
3. I don't care how current cinder + qemu code works, just write new one for linux kernel, it's optimal to use userland apps, just add wrappers (no, it's not);
4. Current Cinder integration require zero configuration on oVirt hosts. It's lazy, why oVirt administrator do nothing? just write manual how-to install packages - oVirt administrators love anything except "reinstall" from engine (no, it's not);
5. We broke old code. New features is "Cinderlib is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production".
6. Oh, we broke old code. Let's deprecate them and close PRODUCTION issues (we didn't see anything).
And again, we are not hate new cinderlib integration. We just want that new technology don't break all PRODUCTION clustes. Almost two years ago I write on this issue https://bugzilla.redhat.com/show_bug.cgi?id=1539837#c6 about "before deprecate, let's help to migrate". For now I see that oVirt totally will disable QEMU RBD support and want to use kernel RBD module + python os-brick + userland mappers + shell wrappers.
Thanks, I hope I am writing this for a reason and it will help build bridges between the community and the developers. We have been with oVirt for almost 10 years and now it is a crossroads towards a different virtualization manager.
k
So I see only regressions for now, hope we'll found some code owner who can catch this oVirt 4.4 only bugs.
I looked at the bugs and I see you've already identified the problem and have patches attached, if you can submit the patches and verify them perhaps we can merge the fixes
Currently integration don't need nbd or krbd. Just qemu process. k Sent from my iPhone
On 28 Dec 2020, at 15:28, Benny Zlotnik <bzlotnik@redhat.com> wrote:
On Tue, Dec 22, 2020 at 6:33 PM Konstantin Shalygin <k0ste@k0ste.ru> wrote:
Sandro, FYI we are not against cinderlib integration, more than we are upgrade 4.3 to 4.4 due movement to cinderlib.
But (!) current Managed Storage Block realization support only krbd (kernel RBD) driver - it's also not a option, because kernel client is always lagging behind librbd, and every update\bugfix we should reboot whole host instead simple migration of all VMs and then migrate it back. Also with krbd host will be use kernel page cache, and will not be unmounted if VM will crash (qemu with librbd is one userland process).
There was rbd-nbd support at some point in cinderlib[1] which addresses your concerns, but it was removed because of some issues
+Gorka, are there any plans to pick it up again?
[1] https://github.com/Akrog/cinderlib/commit/a09a7e12fe685d747ed390a59cd42d0acd...
So for me current situation look like this:
1. We update deprecated OpenStack code? Why, Its for delete?.. Nevermind, just update this code...
2. Hmm... auth tests doesn't work, to pass test just disable any OpenStack project_id related things... and... Done...
3. I don't care how current cinder + qemu code works, just write new one for linux kernel, it's optimal to use userland apps, just add wrappers (no, it's not);
4. Current Cinder integration require zero configuration on oVirt hosts. It's lazy, why oVirt administrator do nothing? just write manual how-to install packages - oVirt administrators love anything except "reinstall" from engine (no, it's not);
5. We broke old code. New features is "Cinderlib is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production".
6. Oh, we broke old code. Let's deprecate them and close PRODUCTION issues (we didn't see anything).
And again, we are not hate new cinderlib integration. We just want that new technology don't break all PRODUCTION clustes. Almost two years ago I write on this issue https://bugzilla.redhat.com/show_bug.cgi?id=1539837#c6 about "before deprecate, let's help to migrate". For now I see that oVirt totally will disable QEMU RBD support and want to use kernel RBD module + python os-brick + userland mappers + shell wrappers.
Thanks, I hope I am writing this for a reason and it will help build bridges between the community and the developers. We have been with oVirt for almost 10 years and now it is a crossroads towards a different virtualization manager.
k
So I see only regressions for now, hope we'll found some code owner who can catch this oVirt 4.4 only bugs.
I looked at the bugs and I see you've already identified the problem and have patches attached, if you can submit the patches and verify them perhaps we can merge the fixes _______________________________________________ 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/E7QTTECXLUD6LI...
On 28/12, Benny Zlotnik wrote:
On Tue, Dec 22, 2020 at 6:33 PM Konstantin Shalygin <k0ste@k0ste.ru> wrote:
Sandro, FYI we are not against cinderlib integration, more than we are upgrade 4.3 to 4.4 due movement to cinderlib.
But (!) current Managed Storage Block realization support only krbd (kernel RBD) driver - it's also not a option, because kernel client is always lagging behind librbd, and every update\bugfix we should reboot whole host instead simple migration of all VMs and then migrate it back. Also with krbd host will be use kernel page cache, and will not be unmounted if VM will crash (qemu with librbd is one userland process).
There was rbd-nbd support at some point in cinderlib[1] which addresses your concerns, but it was removed because of some issues
+Gorka, are there any plans to pick it up again?
[1] https://github.com/Akrog/cinderlib/commit/a09a7e12fe685d747ed390a59cd42d0acd...
Hi, Apologies for the delay on the response, I was on a long PTO and came back just yesterday. There are plans to add it now. ;-) I will add the RBD-NBD support to cinderlib and update this thread once there's an RDO RPM available (which usually happens on the same day the patch merges). If using QEMU to directly connect RBD volumes is the preferred option, then that code would have to be added to oVirt and can be done now without any cinderlib changes. The connection information is provided by cinderlib, and oVirt can check the type of connection that is is and do the connection directly in QEMU for RBD volumes, or call os-brick for all other types of volumes to get a local device before adding it to the instances. Cheers, Gorka.
So for me current situation look like this:
1. We update deprecated OpenStack code? Why, Its for delete?.. Nevermind, just update this code...
2. Hmm... auth tests doesn't work, to pass test just disable any OpenStack project_id related things... and... Done...
3. I don't care how current cinder + qemu code works, just write new one for linux kernel, it's optimal to use userland apps, just add wrappers (no, it's not);
4. Current Cinder integration require zero configuration on oVirt hosts. It's lazy, why oVirt administrator do nothing? just write manual how-to install packages - oVirt administrators love anything except "reinstall" from engine (no, it's not);
5. We broke old code. New features is "Cinderlib is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production".
6. Oh, we broke old code. Let's deprecate them and close PRODUCTION issues (we didn't see anything).
And again, we are not hate new cinderlib integration. We just want that new technology don't break all PRODUCTION clustes. Almost two years ago I write on this issue https://bugzilla.redhat.com/show_bug.cgi?id=1539837#c6 about "before deprecate, let's help to migrate". For now I see that oVirt totally will disable QEMU RBD support and want to use kernel RBD module + python os-brick + userland mappers + shell wrappers.
Thanks, I hope I am writing this for a reason and it will help build bridges between the community and the developers. We have been with oVirt for almost 10 years and now it is a crossroads towards a different virtualization manager.
k
So I see only regressions for now, hope we'll found some code owner who can catch this oVirt 4.4 only bugs.
I looked at the bugs and I see you've already identified the problem and have patches attached, if you can submit the patches and verify them perhaps we can merge the fixes
I understood, more than the code that works with qemu already exists for openstack integration k Sent from my iPhone
On 14 Jan 2021, at 09:43, Gorka Eguileor <geguileo@redhat.com> wrote:
If using QEMU to directly connect RBD volumes is the preferred option, then that code would have to be added to oVirt and can be done now without any cinderlib changes.
On Thu, Jan 21, 2021 at 8:50 AM Konstantin Shalygin <k0ste@k0ste.ru> wrote:
I understood, more than the code that works with qemu already exists for openstack integration
We have code on vdsm and engine to support librbd, but using in cinderlib based volume is not a trivial change. On engine side, this means changing the flow, so instead of attaching a device to a host, engine will configure the xml with network disk, using the rbd url, same way as old cinder support was using. To make this work, engine needs to configure the ceph authentication secrets on all hosts in the DC. We have code to do this for old cinder storage doman, but it is not used for new cinderlib setup. I'm not sure how easy is to use the same mechanism for cinderlib. Generally, we don't want to spend time on special code for ceph, and prefer to outsource this to os brick and the kernel, so we have a uniform way to use volumes. But if the special code gives important benefits, we can consider it. I think openshift virtualization is using the same solution (kernel based rbd) for ceph. An important requirement for us is having an easy way to migrate vms from ovirt to openshift virtuations. Using the same ceph configuration can make this migration easier. I'm also not sure about the future of librbd support in qemu. I know that qemu folks also want to get rid of such code. For example libgfapi (Glsuter native driver) is not maintained and likely to be removed soon. If this feature is important to you, please open RFE for this, and explain why it is needed. We can consider it for future 4.4.z release. Adding some storage and qemu folks to get more info on this. Nir
On 21/01, Nir Soffer wrote:
On Thu, Jan 21, 2021 at 8:50 AM Konstantin Shalygin <k0ste@k0ste.ru> wrote:
I understood, more than the code that works with qemu already exists for openstack integration
We have code on vdsm and engine to support librbd, but using in cinderlib based volume is not a trivial change.
On engine side, this means changing the flow, so instead of attaching a device to a host, engine will configure the xml with network disk, using the rbd url, same way as old cinder support was using.
To make this work, engine needs to configure the ceph authentication secrets on all hosts in the DC. We have code to do this for old cinder storage doman, but it is not used for new cinderlib setup. I'm not sure how easy is to use the same mechanism for cinderlib.
Hi, All the data is in the connection info (including the keyring), so it should be possible to implement.
Generally, we don't want to spend time on special code for ceph, and prefer to outsource this to os brick and the kernel, so we have a uniform way to use volumes. But if the special code gives important benefits, we can consider it.
I think think that's reasonable. Having less code to worry about and making the project's code base more readable and maintainable is a considerable benefit that should not be underestimated.
I think openshift virtualization is using the same solution (kernel based rbd) for ceph. An important requirement for us is having an easy way to migrate vms from ovirt to openshift virtuations. Using the same ceph configuration can make this migration easier.
The Ceph CSI plugin seems to have the possibility of using krbd and rbd-nbd [1], but that's something we can also achieve in oVirt by adding back the rbd-nbd support in cinderlib without changes to oVirt. Cheers, Gorka. [1]: https://github.com/ceph/ceph-csi/blob/04644c1d5896b493d6aaf9ab66f2302cf67a2e...
I'm also not sure about the future of librbd support in qemu. I know that qemu folks also want to get rid of such code. For example libgfapi (Glsuter native driver) is not maintained and likely to be removed soon.
If this feature is important to you, please open RFE for this, and explain why it is needed.
We can consider it for future 4.4.z release.
Adding some storage and qemu folks to get more info on this.
Nir
I would love https://github.com/openstack/cinderlib/commit/a09a7e12fe685d747ed390a59cd42d... to come back. On Thu, Jan 21, 2021 at 2:27 PM Gorka Eguileor <geguileo@redhat.com> wrote:
On 21/01, Nir Soffer wrote:
On Thu, Jan 21, 2021 at 8:50 AM Konstantin Shalygin <k0ste@k0ste.ru> wrote:
I understood, more than the code that works with qemu already exists
for openstack integration
We have code on vdsm and engine to support librbd, but using in cinderlib based volume is not a trivial change.
On engine side, this means changing the flow, so instead of attaching a device to a host, engine will configure the xml with network disk, using the rbd url, same way as old cinder support was using.
To make this work, engine needs to configure the ceph authentication secrets on all hosts in the DC. We have code to do this for old cinder storage doman, but it is not used for new cinderlib setup. I'm not sure how easy is to use the same mechanism for cinderlib.
Hi,
All the data is in the connection info (including the keyring), so it should be possible to implement.
Generally, we don't want to spend time on special code for ceph, and
prefer
to outsource this to os brick and the kernel, so we have a uniform way to use volumes. But if the special code gives important benefits, we can consider it.
I think think that's reasonable. Having less code to worry about and making the project's code base more readable and maintainable is a considerable benefit that should not be underestimated.
I think openshift virtualization is using the same solution (kernel based rbd) for ceph. An important requirement for us is having an easy way to migrate vms from ovirt to openshift virtuations. Using the same ceph configuration can make this migration easier.
The Ceph CSI plugin seems to have the possibility of using krbd and rbd-nbd [1], but that's something we can also achieve in oVirt by adding back the rbd-nbd support in cinderlib without changes to oVirt.
Cheers, Gorka.
[1]: https://github.com/ceph/ceph-csi/blob/04644c1d5896b493d6aaf9ab66f2302cf67a2e...
I'm also not sure about the future of librbd support in qemu. I know that qemu folks also want to get rid of such code. For example libgfapi (Glsuter native driver) is not maintained and likely to be removed soon.
If this feature is important to you, please open RFE for this, and explain why it is needed.
We can consider it for future 4.4.z release.
Adding some storage and qemu folks to get more info on this.
Nir
_______________________________________________ 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/SUXZT47HWHALTY...
All connection data should be comes from cinderlib, as for current cinder integration. Gorka says the same Thanks, k Sent from my iPhone
On 21 Jan 2021, at 16:54, Nir Soffer <nsoffer@redhat.com> wrote:
To make this work, engine needs to configure the ceph authentication secrets on all hosts in the DC. We have code to do this for old cinder storage doman, but it is not used for new cinderlib setup. I'm not sure how easy is to use the same mechanism for cinderlib.
On 12/21/2020 8:22 AM, Sandro Bonazzola wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
...
This release is available now on x86_64 architecture for:
*
Red Hat Enterprise Linux 8.3
*
CentOS Linux (or similar) 8.3
*
CentOS Stream (tech preview)
Sandro, I have a question about "Red Hat Enterprise Linux" compatibility with oVirt. I've always used CentOS in the past along with oVirt. I'm running CentOS 7 along with oVirt 4.3. I really want to upgrade to oVirt 4.4, but I'm not comfortable with the future vision for CentOS as it stands for my virtualization platform. If I was to move to RHEL for my oVirt systems, but still stick with the "self supported" model, it's not clear whether I can get away with using "RHEL Workstation" for my 4 hosts ($179 USD each), or whether I need to purchase "Red Hat Enterprise Linux Server" ($349 USD each). Any feedback would be appreciated. Thanks! Jason.
On 12/21/2020 8:22 AM, Sandro Bonazzola wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
...
This release is available now on x86_64 architecture for:
*
Red Hat Enterprise Linux 8.3
*
CentOS Linux (or similar) 8.3
*
CentOS Stream (tech preview)
Sandro, I have a question about "Red Hat Enterprise Linux" compatibility with oVirt. I've always used CentOS in the past along with oVirt. I'm running CentOS 7 along with oVirt 4.3. I really want to upgrade to oVirt 4.4, but I'm not comfortable with the future vision for CentOS as it stands for my virtualization platform. If I was to move to RHEL for my oVirt systems, but still stick with the "self supported" model, it's not clear whether I can get away with using "RHEL Workstation" for my 4 hosts ($179 USD each), or whether I need to purchase "Red Hat Enterprise Linux Server" ($349 USD each). Any feedback would be appreciated. Thanks! Jason. PS: I had sent the above with my other email accidentally .. list moderator can delete.
Il giorno mar 22 dic 2020 alle ore 07:51 Jason Keltz <jas@yorku.ca> ha scritto:
On 12/21/2020 8:22 AM, Sandro Bonazzola wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
...
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.3 -
CentOS Linux (or similar) 8.3 -
CentOS Stream (tech preview)
Sandro,
I have a question about "Red Hat Enterprise Linux" compatibility with oVirt. I've always used CentOS in the past along with oVirt. I'm running CentOS 7 along with oVirt 4.3. I really want to upgrade to oVirt 4.4, but I'm not comfortable with the future vision for CentOS as it stands for my virtualization platform. If I was to move to RHEL for my oVirt systems, but still stick with the "self supported" model, it's not clear whether I can get away with using "RHEL Workstation" for my 4 hosts ($179 USD each), or whether I need to purchase "Red Hat Enterprise Linux Server" ($349 USD each). Any feedback would be appreciated.
I would like to remind the list that more than one year ago the oVirt project announced that CentOS Stream would be the preferred upstream platform on which oVirt should be run ( https://blogs.ovirt.org/2019/09/ovirt-and-centos-stream/). We are going to keep oVirt tested continuously on CentOS Stream in our CI environments so we expect the combination of oVirt and CentOS Stream to be stable also for production systems. That said, I understand the reason for choosing to move to an alternative to CentOS Linux and I appreciate the choice of Red Hat Enterprise Linux. From a technical point of view, RHEL Workstation should work fine but I'm not an expert about subscriptions entitlements.
Thanks!
Jason.
PS: I had sent the above with my other email accidentally .. list moderator can delete. _______________________________________________ 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/XFFF6LASXL3VVL...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
You can use OEL or any EL-based clone. Best Regards, Strahil Nikolov В вторник, 22 декември 2020 г., 08:46:54 Гринуич+2, Jason Keltz <jas@eecs.yorku.ca> написа: On 12/21/2020 8:22 AM, Sandro Bonazzola wrote:
oVirt 4.4.4 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020. ...
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * CentOS Stream (tech preview)
Sandro, I have a question about "Red Hat Enterprise Linux" compatibility with oVirt. I've always used CentOS in the past along with oVirt. I'm running CentOS 7 along with oVirt 4.3. I really want to upgrade to oVirt 4.4, but I'm not comfortable with the future vision for CentOS as it stands for my virtualization platform. If I was to move to RHEL for my oVirt systems, but still stick with the "self supported" model, it's not clear whether I can get away with using "RHEL Workstation" for my 4 hosts ($179 USD each), or whether I need to purchase "Red Hat Enterprise Linux Server" ($349 USD each). Any feedback would be appreciated. Thanks! Jason. _______________________________________________ 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/TB6TOM2RGRJGXX...
Hi, I think the big question is: Will ovirt be tested against such EL-based clones. Is ovirt then still 100% compatible to EL, when it will be developed for Stream, because Stream will be ahead EL. Next question is, how stable will be CentOS stream? At the moment, ovirt is using a lot a packages of different 3rd party repos, but the OS system core is still EL clone and stable. With stream, also the core system is quite new and a way newer than EL, so how stable will it be? Can you then still use CentOS stream + oVirt in production systems? BR Florian ----- Ursprüngliche Mail ----- Von: "users" <users@ovirt.org> An: "users" <users@ovirt.org>, "Jason Keltz" <jas@eecs.yorku.ca> Gesendet: Dienstag, 22. Dezember 2020 12:20:04 Betreff: [ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available You can use OEL or any EL-based clone. Best Regards, Strahil Nikolov В вторник, 22 декември 2020 г., 08:46:54 Гринуич+2, Jason Keltz <jas@eecs.yorku.ca> написа: On 12/21/2020 8:22 AM, Sandro Bonazzola wrote:
oVirt 4.4.4 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020. ...
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * CentOS Stream (tech preview)
Sandro, I have a question about "Red Hat Enterprise Linux" compatibility with oVirt. I've always used CentOS in the past along with oVirt. I'm running CentOS 7 along with oVirt 4.3. I really want to upgrade to oVirt 4.4, but I'm not comfortable with the future vision for CentOS as it stands for my virtualization platform. If I was to move to RHEL for my oVirt systems, but still stick with the "self supported" model, it's not clear whether I can get away with using "RHEL Workstation" for my 4 hosts ($179 USD each), or whether I need to purchase "Red Hat Enterprise Linux Server" ($349 USD each). Any feedback would be appreciated. Thanks! Jason. _______________________________________________ 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/TB6TOM2RGRJGXX... _______________________________________________ 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/34LBTODBJX25TN...
Il giorno mar 22 dic 2020 alle ore 13:57 Florian Schmid via Users < users@ovirt.org> ha scritto:
Hi,
I think the big question is: Will ovirt be tested against such EL-based clones.
Well, it will be tested for those EL-based clones a few months before they'll be released, being CentOS Stream upstream to those clones. At GA time, oVirt is already expected to work fine on latest Red Hat Enterprise Linux. The gain on using CentOS Stream is that it will be already working also on next Red Hat Enterprise Linux.
Is ovirt then still 100% compatible to EL, when it will be developed for Stream, because Stream will be ahead EL.
I don't see why it shouldn't. As an example scenario: - oVirt 4.4.3 has been released with cluster compatibility level 4.5, requiring RHEL 8.3 + Advanced Virtualization to be able to consume the new feature. But it worked fine on CentOS 8.2 in cluster compatibility level 4.4. - CentOS 8.3 and Advanced Virtualization 8.3 got released: 4.4.3 and the new 4.4.4 can now use cluster level 4.5. With CentOS Stream you'll get similar scenario. At GA time oVirt 4.4.5 will be released working with CentOS Stream at release date which basically means, it will be ready to work on RHEL 8.4 but will be working with RHEL 8.3 too while waiting for RHEL 8.4 to be released.
Next question is, how stable will be CentOS stream?
I think pretty much. Before landing on CentOS Stream packages have been already through RHEL CI. And oVirt wise, it will go through our CI as well.
At the moment, ovirt is using a lot a packages of different 3rd party repos, but the OS system core is still EL clone and stable. With stream, also the core system is quite new and a way newer than EL, so how stable will it be?
Can you then still use CentOS stream + oVirt in production systems?
I think so, and oVirt wise we already foresee CentOS Stream in production more than one year ago: https://blogs.ovirt.org/2019/09/ovirt-and-centos-stream/
BR Florian
----- Ursprüngliche Mail ----- Von: "users" <users@ovirt.org> An: "users" <users@ovirt.org>, "Jason Keltz" <jas@eecs.yorku.ca> Gesendet: Dienstag, 22. Dezember 2020 12:20:04 Betreff: [ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available
You can use OEL or any EL-based clone.
Best Regards, Strahil Nikolov
В вторник, 22 декември 2020 г., 08:46:54 Гринуич+2, Jason Keltz < jas@eecs.yorku.ca> написа:
On 12/21/2020 8:22 AM, Sandro Bonazzola wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
...
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * CentOS Stream (tech preview)
Sandro,
I have a question about "Red Hat Enterprise Linux" compatibility with oVirt. I've always used CentOS in the past along with oVirt. I'm running CentOS 7 along with oVirt 4.3. I really want to upgrade to oVirt 4.4, but I'm not comfortable with the future vision for CentOS as it stands for my virtualization platform. If I was to move to RHEL for my oVirt systems, but still stick with the "self supported" model, it's not clear whether I can get away with using "RHEL Workstation" for my 4 hosts ($179 USD each), or whether I need to purchase "Red Hat Enterprise Linux Server" ($349 USD each). Any feedback would be appreciated.
Thanks!
Jason.
_______________________________________________ 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/TB6TOM2RGRJGXX... _______________________________________________ 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/34LBTODBJX25TN... _______________________________________________ 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/UKQ5CDDWNH2YOD...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
Thx a lot Sandro. Von: "Sandro Bonazzola" <sbonazzo@redhat.com> An: "Florian Schmid" <fschmid@ubimet.com> CC: "users" <users@ovirt.org>, "Jason Keltz" <jas@eecs.yorku.ca>, "Strahil Nikolov" <hunter86_bg@yahoo.com> Gesendet: Dienstag, 22. Dezember 2020 14:14:28 Betreff: Re: [ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available Il giorno mar 22 dic 2020 alle ore 13:57 Florian Schmid via Users < [ mailto:users@ovirt.org | users@ovirt.org ] > ha scritto: Hi, I think the big question is: Will ovirt be tested against such EL-based clones. Well, it will be tested for those EL-based clones a few months before they'll be released, being CentOS Stream upstream to those clones. At GA time, oVirt is already expected to work fine on latest Red Hat Enterprise Linux. The gain on using CentOS Stream is that it will be already working also on next Red Hat Enterprise Linux. BQ_BEGIN Is ovirt then still 100% compatible to EL, when it will be developed for Stream, because Stream will be ahead EL. BQ_END I don't see why it shouldn't. As an example scenario: - oVirt 4.4.3 has been released with cluster compatibility level 4.5, requiring RHEL 8.3 + Advanced Virtualization to be able to consume the new feature. But it worked fine on CentOS 8.2 in cluster compatibility level 4.4. - CentOS 8.3 and Advanced Virtualization 8.3 got released: 4.4.3 and the new 4.4.4 can now use cluster level 4.5. With CentOS Stream you'll get similar scenario. At GA time oVirt 4.4.5 will be released working with CentOS Stream at release date which basically means, it will be ready to work on RHEL 8.4 but will be working with RHEL 8.3 too while waiting for RHEL 8.4 to be released. BQ_BEGIN Next question is, how stable will be CentOS stream? BQ_END I think pretty much. Before landing on CentOS Stream packages have been already through RHEL CI. And oVirt wise, it will go through our CI as well. BQ_BEGIN At the moment, ovirt is using a lot a packages of different 3rd party repos, but the OS system core is still EL clone and stable. With stream, also the core system is quite new and a way newer than EL, so how stable will it be? Can you then still use CentOS stream + oVirt in production systems? BQ_END I think so, and oVirt wise we already foresee CentOS Stream in production more than one year ago: [ https://blogs.ovirt.org/2019/09/ovirt-and-centos-stream/ | https://blogs.ovirt.org/2019/09/ovirt-and-centos-stream/ ] BQ_BEGIN BR Florian ----- Ursprüngliche Mail ----- Von: "users" < [ mailto:users@ovirt.org | users@ovirt.org ] > An: "users" < [ mailto:users@ovirt.org | users@ovirt.org ] >, "Jason Keltz" < [ mailto:jas@eecs.yorku.ca | jas@eecs.yorku.ca ] > Gesendet: Dienstag, 22. Dezember 2020 12:20:04 Betreff: [ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available You can use OEL or any EL-based clone. Best Regards, Strahil Nikolov В вторник, 22 декември 2020 г., 08:46:54 Гринуич+2, Jason Keltz < [ mailto:jas@eecs.yorku.ca | jas@eecs.yorku.ca ] > написа: On 12/21/2020 8:22 AM, Sandro Bonazzola wrote:
oVirt 4.4.4 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020. ...
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * CentOS Stream (tech preview)
Sandro, I have a question about "Red Hat Enterprise Linux" compatibility with oVirt. I've always used CentOS in the past along with oVirt. I'm running CentOS 7 along with oVirt 4.3. I really want to upgrade to oVirt 4.4, but I'm not comfortable with the future vision for CentOS as it stands for my virtualization platform. If I was to move to RHEL for my oVirt systems, but still stick with the "self supported" model, it's not clear whether I can get away with using "RHEL Workstation" for my 4 hosts ($179 USD each), or whether I need to purchase "Red Hat Enterprise Linux Server" ($349 USD each). Any feedback would be appreciated. Thanks! Jason. _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users@ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave@ovirt.org ] Privacy Statement: [ https://www.ovirt.org/privacy-policy.html | https://www.ovirt.org/privacy-policy.html ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/TB6TOM2RGRJGXX... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/TB6TOM2RGRJGXX... ] _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users@ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave@ovirt.org ] Privacy Statement: [ https://www.ovirt.org/privacy-policy.html | https://www.ovirt.org/privacy-policy.html ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/34LBTODBJX25TN... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/34LBTODBJX25TN... ] _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users@ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave@ovirt.org ] Privacy Statement: [ https://www.ovirt.org/privacy-policy.html | https://www.ovirt.org/privacy-policy.html ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/UKQ5CDDWNH2YOD... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/UKQ5CDDWNH2YOD... ] BQ_END -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV [ https://www.redhat.com/ | Red Hat EMEA ] [ mailto:sbonazzo@redhat.com | sbonazzo@redhat.com ] [ https://www.redhat.com/ ] [ https://mojo.redhat.com/docs/DOC-1199578 | Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. ]
Hello, considering we want to do a new oVirt&gluster hyper-converged deployment on CentOS for a production environment what should we do regarding the OS? Considering Centos Stream is on tech preview and Centos 8 is near EOL, what is the correct path? Install CentOS 8.3 and use it until EOL and then update the hosts to centos stream when it becomes stable? install CentOS Stream even though it is on tech preview? Regards! Bernardo PGP Key <http://pgp.key-server.io/0x695E5BCE34263F5B> On Mon, Dec 21, 2020 at 10:32 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade
Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported.
For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJN... ) Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. -
For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. -
For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. -
For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>.
What’s new in oVirt 4.4.4 Release?
This update is the fourth in a series of stabilization updates to the 4.4 series.
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.3 -
CentOS Linux (or similar) 8.3 -
CentOS Stream (tech preview)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:
-
Red Hat Enterprise Linux 8.3 -
CentOS Linux (or similar) 8.3 -
oVirt Node (based on CentOS Linux 8.3) -
CentOS Stream (tech preview)
oVirt Node and Appliance have been updated, including:
-
oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/ -
Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9...
-
CentOS Linux 8 (2011): https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html -
Advanced Virtualization 8.3
See the release notes [1] for installation instructions and a list of new features and bugs fixed.
Notes:
-
oVirt Appliance is already available for CentOS Linux 8 -
oVirt Node NG is already available for CentOS Linux 8
Additional resources:
-
Read more about the oVirt 4.4.4 release highlights: https://www.ovirt.org/release/4.4.4/ -
Get more oVirt project updates on Twitter: https://twitter.com/ovirt -
Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/
[1] https://www.ovirt.org/release/4.4.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@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.*
_______________________________________________ Announce mailing list -- announce@ovirt.org To unsubscribe send an email to announce-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/announce@ovirt.org/message/KMYD2GAHZXW...
Hi Bernardo, I think that when CentOS Stream 9 (and all EL 9 clones) come up - oVirt will switch , so I think it's worth trying the Stream (but no earlier than April). Best Regards, Strahil Nikolov В неделя, 10 януари 2021 г., 09:32:01 Гринуич+2, Bernardo Juanicó <bjuanico@gmail.com> написа: Hello, considering we want to do a new oVirt&gluster hyper-converged deployment on CentOS for a production environment what should we do regarding the OS? Considering Centos Stream is on tech preview and Centos 8 is near EOL, what is the correct path? Install CentOS 8.3 and use it until EOL and then update the hosts to centos stream when it becomes stable? install CentOS Stream even though it is on tech preview? Regards! Bernardo PGP Key On Mon, Dec 21, 2020 at 10:32 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJN... ) Documentation * If you want to try oVirt as quickly as possible, follow the instructions on the Download page. * For complete installation, administration, and usage instructions, see the oVirt Documentation. * For upgrading from a previous version, see the oVirt Upgrade Guide. * For a general overview of oVirt, see About oVirt. What’s new in oVirt 4.4.4 Release? This update is the fourth in a series of stabilization updates to the 4.4 series.
This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * CentOS Stream (tech preview)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * oVirt Node (based on CentOS Linux 8.3) * CentOS Stream (tech preview)
oVirt Node and Appliance have been updated, including: * oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/ * Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9... * CentOS Linux 8 (2011): https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html * Advanced Virtualization 8.3
See the release notes [1] for installation instructions and a list of new features and bugs fixed.
Notes: * oVirt Appliance is already available for CentOS Linux 8 * oVirt Node NG is already available for CentOS Linux 8
Additional resources: * Read more about the oVirt 4.4.4 release highlights: https://www.ovirt.org/release/4.4.4/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/
[1] https://www.ovirt.org/release/4.4.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
-- 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.
_______________________________________________ Announce mailing list -- announce@ovirt.org To unsubscribe send an email to announce-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/announce@ovirt.org/message/KMYD2GAHZXW...
_______________________________________________ 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/4DC7SK4L6AYEVM...
Il giorno lun 11 gen 2021 alle ore 06:04 Strahil Nikolov via Users < users@ovirt.org> ha scritto:
Hi Bernardo,
I think that when CentOS Stream 9 (and all EL 9 clones) come up - oVirt will switch , so I think it's worth trying the Stream (but no earlier than April).
There are no current plans to switch to CentOS Stream 9. Currently we are targeting CentOS Stream 8.
Best Regards, Strahil Nikolov
В неделя, 10 януари 2021 г., 09:32:01 Гринуич+2, Bernardo Juanicó < bjuanico@gmail.com> написа:
Hello, considering we want to do a new oVirt&gluster hyper-converged deployment on CentOS for a production environment what should we do regarding the OS? Considering Centos Stream is on tech preview and Centos 8 is near EOL, what is the correct path? Install CentOS 8.3 and use it until EOL and then update the hosts to centos stream when it becomes stable? install CentOS Stream even though it is on tech preview?
Regards! Bernardo PGP Key
On Mon, Dec 21, 2020 at 10:32 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
oVirt 4.4.4 is now generally available
The oVirt project is excited to announce the general availability of
oVirt 4.4.4 , as of December 21st, 2020.
This release unleashes an altogether more powerful and flexible open
Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list
source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJN... )
Documentation * If you want to try oVirt as quickly as possible, follow the instructions on the Download page. * For complete installation, administration, and usage instructions, see the oVirt Documentation. * For upgrading from a previous version, see the oVirt Upgrade Guide. * For a general overview of oVirt, see About oVirt. What’s new in oVirt 4.4.4 Release? This update is the fourth in a series of stabilization updates to the 4.4 series.
This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * CentOS Stream (tech preview)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 * CentOS Linux (or similar) 8.3 * oVirt Node (based on CentOS Linux 8.3) * CentOS Stream (tech preview)
oVirt Node and Appliance have been updated, including: * oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/ * Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9...
* CentOS Linux 8 (2011):
https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html
* Advanced Virtualization 8.3
See the release notes [1] for installation instructions and a list of
new features and bugs fixed.
Notes: * oVirt Appliance is already available for CentOS Linux 8 * oVirt Node NG is already available for CentOS Linux 8
Additional resources: * Read more about the oVirt 4.4.4 release highlights:
https://www.ovirt.org/release/4.4.4/
* Get more oVirt project updates on Twitter:
* Check out the latest project news on the oVirt blog:
[1] https://www.ovirt.org/release/4.4.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
-- 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.
_______________________________________________ Announce mailing list -- announce@ovirt.org To unsubscribe send an email to announce-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/announce@ovirt.org/message/KMYD2GAHZXW...
_______________________________________________ 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/4DC7SK4L6AYEVM... _______________________________________________ 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/W4J256DUWCJGXL...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
Il giorno dom 10 gen 2021 alle ore 08:33 Bernardo Juanicó < bjuanico@gmail.com> ha scritto:
Hello, considering we want to do a new oVirt&gluster hyper-converged deployment on CentOS for a production environment what should we do regarding the OS? Considering Centos Stream is on tech preview and Centos 8 is near EOL, what is the correct path? Install CentOS 8.3 and use it until EOL and then update the hosts to centos stream when it becomes stable? install CentOS Stream even though it is on tech preview?
Up to oVirt 4.4.4 please keep using CentOS Linux 8. With oVirt 4.4.5 we are developing oVirt Appliance and oVirt Node based on CentOS Stream 8. We'll release 4.4.5 when all known issues on CentOS Stream 8 will be addressed. At that point CentOS Stream will be the recommended platform to run oVirt.
Regards! Bernardo PGP Key <http://pgp.key-server.io/0x695E5BCE34263F5B>
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@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>*
participants (14)
-
Benny Zlotnik -
Bernardo Juanicó -
Eyal Shenitzky -
Florian Schmid -
Gianluca Cecchi -
Gorka Eguileor -
Jason Keltz -
Jason Keltz -
Konstantin Shalygin -
Matthias Leopold -
Nir Soffer -
Sandro Bonazzola -
Shantur Rathore -
Strahil Nikolov