Hi Michal, Actually you can manually install the packages from earlier (sub-)versions since these are still in the repo, however I don't really see the reason to do so. Once the new stable version is released it's recommended to install that version. Do you think it can be usable to actually maintain separate repos for each sub-versions that we release? E.g. 4.1.1, 4.1.2, etc. etc. ? If so, for which practical use ? Thanks in advance, On Tue, Aug 29, 2017 at 10:52 AM, Michal Skrivanek < michal.skrivanek@redhat.com> wrote:

On 22 Aug 2017, at 16:45, Lev Veyde <lveyde@redhat.com> wrote:

The oVirt Project is pleased to announce the availability of the General Availability Release of oVirt 4.1.5, as of August 22nd, 2017

This update is the fifth in a series of stabilization updates to the 4.1 series. 4.1.5 brings more than 20 enhancements and more than 90 bugfixes, including more than 40 high or urgent severity fixes, on top of oVirt 4.1 series

I was a bit surprised to find out that the repo content is always replaced. There is no way how to install 4.1.4 anymore? Or any package from 4.1.4. This sounds quite unusual

Starting 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a real performance boost for ovirt when using GlusterFS . Due to a known issue [6], using this will break live storage migration. This is expected to be fixed soon. If you do not use live storage migration you can give it a try. Use [7] for more details on how to enable it.

This release is available now for: * Fedora 24 (tech preview)

do we still want to say that when F24 is EOL?

* Red Hat Enterprise Linux 7.3 or later

I know “or later” covers that, but it might make sense to explicitly mention RHEL 7.4 is the tested baseline

Thanks, michal

* CentOS Linux (or similar) 7.3 or later

This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later

* CentOS Linux (or similar) 7.3 or later * oVirt Node 4.1 * Fedora 24 (tech preview)

See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed.

Notes: - oVirt Appliance is already available - oVirt Live is already available[4] - oVirt Node is already available[4]

Additional Resources: * Read more about the oVirt 4.1.5 release highlights: http://www.ovirt.org/release/4.1.5/ * 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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.5/ [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/ [5] http://staged-gluster-docs.readthedocs.io/en/release3.7. 0beta1/Features/libgfapi/ [6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562 [7] http://www.ovirt.org/develop/release-management/features/ storage/glusterfs-storage-domain/

Thanks in advance, --

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel

<https://www.redhat.com/>

lev@redhat.com | lveyde@redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

-- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev@redhat.com | lveyde@redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>