RHEV-H 6.2 Hypervisor Future distribution details

Latest response




currently i am running RHEV-M 3.0 and RHEV-H 6.2 as the combination.

what will be next release of RHEV-H. will it be similar to RHEL 6 release. so it be RHEV-H 6.3 ??

if so for every release of RHEL6, will an RHEV-H will be released????





RHEV-H has it's own release cycle, but it's closely coupled with RHEL, so yes, with RHEL6.3 a RHEV-H based on 6.3 will come out. The same goes for critical and relevant hotfixes that are released for RHEL - when something is available, a new RHEV-H ISO gets spinned and becomes available.


Besides, new RHEV-H spins can be released if an important hotfix that is specific to RHEV-H comes out.

That's not entirely correct.  RHEV-H does not have its own release cycle.  It is part of the RHEL release cycle, not just tied tightly to it.  


It is considered to be another variant of RHEL.  With every major and minor release of RHEL, a new version of RHEV-H is released on the same date.  In addition, RHEV-H follows the beta and release candidate schedule for RHEL as well.


For asynchronous updates, RHEV-H follows the kernel update cadence, releasing a new ISO just after each kernel update is released.  That way we always make sure to have the latest kernels in a released ISO for RHEV-H.  Sometimes these RHEV-H updates are released quite close to the kernel update date, and sometimes there might be a bit of a lag (a few days, a week) while testing of the new kernel is completed in the RHEV-H build.

What is the process for a critical security update?  So a new ISO image cut?  It is rare but it does happen that something is found that is critical and can't wait for the next scheduled release cycle.  Enterprise customers often expect or even demand critical fixes are slipstreamed into media or incremental updates in less than 24 hours, and usually have a policy internally that requires their entire (at risk) infrastructure to be updated with in 24 hours.  So there needs to be a way to update RHEV-H very quickly with ease, else, enterprise customers that have this this ability with other solutions, may discount RHEV for this lack of feasibility.

If a critical security issue is found that would have an impact on RHEV-H, we would release an asynchronous update of RHEV-H via a new ISO.  This is the same policy that happens with the kernel as well.  Normal kernel releases are on a fairly set schedule (approx 6 week cadence) but if a critical security issue is found, a kernel can be released outside of that normal cadence.  The same holds for RHEV-H.

RHEV-H is essentially an appliance, when a critical issue is fixed, RHEV-H is respinned, and a new ISO is released.

Updating RHEV-H is very simple - just download the new ISO to RHEV-M, put host in maintenance and upgrade right in the GUI