oVirt 4.4.0 Beta release is now available for testing The oVirt Project is excited to announce the availability of the beta release of oVirt 4.4.0 for testing, as of March 27th, 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 on top of oVirt 4.3. Important notes before you try it Please note this is a Beta release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. In particular, please note that upgrades from 4.3 and future upgrades from this beta to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Beta require content that will be available in CentOS Linux 8.2 which are currently included in Red Hat Enterprise Linux 8.2 beta. If you want to have a better experience you can test oVirt 4.4.0 Beta on Red Hat Enterprise Linux 8.2 beta. Known Issues - ovirt-imageio development is still in progress. In this beta you can’t upload images to data domains. You can still copy iso images into the deprecated ISO domain for installing VMs.

Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-... - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps 389-ds - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-... ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0 Beta? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support

- Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>;. In such a case, please be sure to take the qc2 image and not the ova image. 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.0 release highlights: http://www.ovirt.org/release/4.4.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *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(a)ovirt.org To unsubscribe send an email to users-leave(a)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/LB4I6OEO5EC...

On 27-3-2020 15:48, Sandro Bonazzola wrote: oVirt 4.4.0 Beta release is now available for testing The oVirt Project is excited to announce the availability of the beta release of oVirt 4.4.0 for testing, as of March 27th, 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 on top of oVirt 4.3. Important notes before you try it Please note this is a Beta release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. In particular, please note that upgrades from 4.3 and future upgrades from this beta to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Beta require content that will be available in CentOS Linux 8.2 which are currently included in Red Hat Enterprise Linux 8.2 beta. If you want to have a better experience you can test oVirt 4.4.0 Beta on Red Hat Enterprise Linux 8.2 beta. Known Issues - ovirt-imageio development is still in progress. In this beta you can’t upload images to data domains. You can still copy iso images into the deprecated ISO domain for installing VMs. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from <http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-... http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-... - dnf install <https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm> https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps 389-ds - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from <http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-... http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-... ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. I have tested the HCI setup but ran into a problem at the the end of the storage step.

What I did is follow https://ovirt.org/download/beta.html Host is Centos-8.1 from above both steps done, no problem Install oVirt using the Cockpit wizard 1 - not needed as its CentOS 2 - 5 no problems, BUT Cockpit session timeout if you're not careful, fix: (add [Session] IdleTimeout=0 in /etc/cockpit/cockpit.conf )

AND If using step 6 and then choosing HCI setup the following is observed: Deploy fails at certain steps because missing: - hostname not in /etc/hosts - gluster-ansible-roles not installed - glusterfs-server not installed (firewall service name not available) - vdsm-gluster (don't now if its needed but sounds logical) - ssh-keygen - ssh-copy-id `hostname -f` --> dnf install gluster-ansible-roles glusterfs-server vdsm-gluster -y

If the above is in place than gluster deploy will succeed and the hosted-engine deploy will succeed but the storage step fails when it tries to access glusterfs. I can't find the reason in the logs and maybe I'm looking at the wrong one. The wizard doesn't copy all relevant logs when it encounters an error as it did in the alpha release, atleast not at this point, never got to here in the alpha.

Following is attached: From engine: /var/log/ovirt-engine From host: /var/log/glusterfs and /var/log/ovirt-hosted-engine-setup I can provide further logs if needed. Thanks in advance, Joop _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/W66U3XJODSM...

Il giorno lun 30 mar 2020 alle ore 16:56 Joop <jvdwege(a)xs4all.nl <mailto:jvdwege@xs4all.nl>> ha scritto: On 27-3-2020 15:48, Sandro Bonazzola wrote: > > > oVirt 4.4.0 Beta release is now available for testing > > > The oVirt Project is excited to announce the availability of the > beta release of oVirt 4.4.0 for testing, as of March 27th, 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 on top of > oVirt 4.3. > > > Important notes before you try it > > Please note this is a Beta release. > > The oVirt Project makes no guarantees as to its suitability or > usefulness. > > This pre-release must not to be used in production. > > In particular, please note that upgrades from 4.3 and future > upgrades from this beta to the final 4.4 release from this > version are not supported. > > Some of the features included in oVirt 4.4.0 Beta require content > that will be available in CentOS Linux 8.2 which are currently > included in Red Hat Enterprise Linux 8.2 beta. If you want to > have a better experience you can test oVirt 4.4.0 Beta on Red Hat > Enterprise Linux 8.2 beta. > > > Known Issues > > * > > ovirt-imageio development is still in progress. In this beta > you can’t upload images to data domains. You can still copy > iso images into the deprecated ISO domain for installing VMs. > > > Installation instructions > > > For the engine: either use appliance or: > > - Install CentOS Linux 8 minimal from > <http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-... > > - dnf install > <https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm>https... > > - dnf update (reboot if needed) > > - dnf module enable -y javapackages-tools pki-deps 389-ds > > - dnf install ovirt-engine > > - engine-setup > > > For the nodes: > > Either use oVirt Node ISO or: > > - Install CentOS Linux 8 from > <http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-...; > select minimal installation > > - dnf install > https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm > > - dnf update (reboot if needed) > > - Attach the host to engine and let it be deployed. > > I have tested the HCI setup but ran into a problem at the the end of the storage step. Thanks for testing and for the feedback! What I did is follow https://ovirt.org/download/beta.html Host is Centos-8.1 from above both steps done, no problem Install oVirt using the Cockpit wizard 1 - not needed as its CentOS 2 - 5 no problems, BUT Cockpit session timeout if you're not careful, fix: (add [Session] IdleTimeout=0 in /etc/cockpit/cockpit.conf ) Yes, we found it too: https://bugzilla.redhat.com/show_bug.cgi?id=1818566 AND If using step 6 and then choosing HCI setup the following is observed: Deploy fails at certain steps because missing: - hostname not in /etc/hosts - gluster-ansible-roles not installed - glusterfs-server not installed (firewall service name not available) - vdsm-gluster (don't now if its needed but sounds logical) - ssh-keygen - ssh-copy-id `hostname -f` --> dnf install gluster-ansible-roles glusterfs-server vdsm-gluster -y adding +Gobinda Das <mailto:godas@redhat.com> here. I think that the HCI deployment has been developed and tested only for oVirt Node consumption, not really supported on plain CentOS installation. Maybe worth to document above steps in HCI deployment doc or make it clear to use oVirt Node instead. If the above is in place than gluster deploy will succeed and the hosted-engine deploy will succeed but the storage step fails when it tries to access glusterfs. I can't find the reason in the logs and maybe I'm looking at the wrong one. The wizard doesn't copy all relevant logs when it encounters an error as it did in the alpha release, atleast not at this point, never got to here in the alpha. Gobinda can you please have a look? +Evgeny Slutsky <mailto:eslutsky@redhat.com> can you have a look too? Following is attached: From engine: /var/log/ovirt-engine From host: /var/log/glusterfs and /var/log/ovirt-hosted-engine-setup I can provide further logs if needed. Thanks in advance, Joop _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto: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/W66U3XJODSM... -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <mailto:sbonazzo@redhat.com> <https://www.redhat.com/> *<https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *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>*