Hi Folks, through the efforts of people much smarter than me Red Hat Virtualization 4 launched today. And nope, that was not a typo.. part of the launch is a re-branding that follows suit with Red Hat’s other products to simplify the naming.
Over the last few weeks, I’ve given you heads up on things like the new hypervisor, the Cockpit hypervisor admin, and a preview on the new RHV-M dashboard. Over the next few weeks, I plan on showing you some of the other new features, such as:
- Advanced Live Migration Policies – greatly reduce the time it takes for a VM to live migrate from one hypervisor to another. For example, a large footprint VM (256GB RAM, 8 CPU, under heavy load) that would previously take many minutes, now takes seconds. I’ll show you how it’s down.
- OpenStack Neutron Integration – have an application that you want to design around both OpenStack and virtualization? Want the front end and middleware to massively scale, but need the backend database to have traditional resources (backup/restore/etc)? You’ll need the networks between RHV and RHOSP to talk efficiently..
- Label Based Affinity – Need to streamline configuration? Have lots of VMs that need to be configured for affinity? Why not configure 1, then label the rest and save time and avoid error?
These are just a few of the things that I’ll be walking through over the next few weeks…
If you’re already a Red Hat Enterprise Virtualization 3.x customer and would like to upgrade, the general process is as follows:
- Apply all updates to RHEV-M 3.x such that is the latest version of 3.6
- Apply all updates to RHEL-H (if you are using the RHEL hypervisor) such that it is the latest version of RHEL 7.2
- RHEV-H hypervisors will need to be completely replaced as they are completely redesigned.
- Use the
engine-backupcommand to backup the entire RHEV-M 3.6 environment. Shutdown the old RHEV-M.
- Create a new RHEL 7.2 VM and deploy RHV-M 4.0 on that new VM.
- Copy the RHEV-M 3.6 backup to the new RHEL 7.2 VM and use the
engine-backupcommand to restore the environment to the new deployment.
- Attach the old data domains to the new deployment.
Not already a user?
If you’re not a Red Hat customer, but still want to see what the deal is, I highly recommend checking out oVirt, which is the upstream project for RHV. All of the development work for RHV is done there.. And as you would expect, there are plenty of non-Red Hat folks doing fantastic Open Source work there too.