Red Hat Virtualization (RHV)

Formerly RHEV

RHEV allow us to install the Operating system image on virtual machines very quickly.

RHEV is an open-source tool, we can easily integrate the solution on any hardware and do a lot of customization.

RHEV is manageable through a Graphical User Interface, which makes it easy for the end-user to manage the RHEV.

Works well on Patching tasks.

Documentation of RHEV needs more improvement.

RHEV GUI needs a lot of improvements in some versions of RHEV, GUI will not work properly (shows incorrect details of VM ).

Need fast rollout of patch releases.

Need good linux Knowledge to manage the RHEVM.

1- It easy to upload qcow2 images from the browser.

2- It is easy to automate repetitive tasks with Ansible using RHVM API.

3- It is easy to patch the hypervisors.

1- RHVM API is pretty slow, especially after creating a VM it is not possible to retrieve the VM details (i.e VM's MAC Address) fast enough, where we need to place a pause in our Ansible Playbook, make the automation process slow.

2- RHV is still using collected to monitor the hypervisors which is deviating from Red Hat policy for other RHEL based applications to use PCP to monitor, which is richer in features.

3- It will be great if it is possible to patch the hypervisors using other tools such as satellite and not only via RHVM.

4- In the past Red Hat used to present patches in the z release (i.e. 4.3.z), and features in the y release (i.e 4. y), but starting from 4.4 that is mixed together wherein the Z release you get both patches and features, that is not good because that requires a lot of time to test when we patch as it includes features as well.

5- Engineering team has to be more reactive when new feature is requested.

RHV issues/bugs can be reported via Bugzilla to RH support. The service is great and typically responds soon.

Red Hat distribution integration is seamless as it is integrated into the kernel.

OpenStack support enables more customized VM templates and network configuration control.

If the aforementioned can't be done, additional open-source tool compatibility or support.

Creating multiple VMs

Save costs as it is open source and comes as Linux kernel Module

Reduces need of multiple hardware everytime you need to scale up

Sometimes it can be complicated to handle

You need support tools for setting up, without it can be complex

Sometimes performance can drop down

Standardisation where provisioning the environment became repeatable and predictable.

Easier debugging and understanding the client system.

Improved security and centrally managed.

Ran into a regression when updating firmware for IGEL

Desktop froze and became non responsive on a few occasions.

Server crashed and took down all the clients in the Thin setup.

Extremely reliable

Easy to maintain in regards to upgrades

RedHat has done a great job for added customization

Open-source so has to be awesome

Great end-user experience

Well done on the Live migration

Saw minor issues during first boot and configuration of VM's

I doubt its a con but you need decent Linux skills to work with this

Could improve and make more user-friendly in terms of UI

Base licensing includes H/A and Live Migration features (you don't have to pay extra for them like VMware).

It's all completely managed through a WebUI - no fat client you have to install.

Very easy to use, manage, provision, and upgrade.

It's definitely come a long ways from what it used to be and is certainly a lot easier - the initial setup/configuration used to be quite difficult but really isn't anymore.

Better support and third-party integration for backup, snapshots, and restore of VMs like VEEAM for VMware - this is my only complaint. There are companies that offer solutions for RHEV however they're very limited and can be pricey.

I think some improvement can be made for deploying micro and cloud services through RHEV.

Providing Virtualization services

Migrating VMs from other virtualization stacks to RHEV

Providing open-source based VDI

Providing a GUI for KVM

Providing HA virtualization

Native Ceph implementation is still missing

Only few software-defined Storage solutions are supported as storage backends

VM management (with virtual hardware, first boot etc.) is a bit fiddly

RHEV can acquire user and group information from an Active Directory service without a great deal of confusing configuration.

RHEV management is browser-based and can be accessed from any platform.

Online Snapshot capability, provides a better redundancy than vSphere.

Hot Swappable functionality could be improved upon.

Template importation from external sources.

Better database synchronization when implemented.

Automation integration

Migration of VMs from one physical host to another

Support for open-source community projects, such as Gluster, Cinder, and Glance

Product Q&A, regression testing, bug fix turnaround

Standardization of deployment between the baseline products (e.g. stand-alone vs. appliance should support same configuration options)

Improve WebUI navigation

Any issues/bugs with RHEV can be fixed by using bugzilla to get in contact with RH support. The support is fantastic and a reply is usually given fairly quickly.

Integration into RedHat distro is seamless as it is already baked into it's kernel.

Support for OpenStack allows for more customization with VM templates and advanced network configuration management.

I would like to see more cloud automated solutions with RHEV with kickstarting nodes without external assistance with tools such as cobbler/foreman.

If the above cant be done, then more compatibility or support for other open source tools.

Integrate with KVM

Python API is easier

integration with puppet and cobbler

better documentation on issues

Faster patch releases

better integration with OVA