Item: Red Hat Virtualization
Rating: 10
Author: Verified User

Use Cases and Deployment Scope

RHEV is used as a one stop solution for virtual environments due to it being part of the RedHat distro.
Business problems that come with this is the costs associated with the implementation of such a solution.

Pros and Cons

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.

Return on Investment

Negative impact due to costs associated with the service contract as we are switching to oVirt due to cutting costs.
Positive impact is that testing on oVirt before purchasing service contracts with RedHat can be done.

Alternatives Considered

oVirt and VMware ESXi

Pretty much Open Source sums it up.

Other Software Used

Puppet Data Center Automation, Blackboard, Jenkins

Likelihood to Recommend

RHEV is most suited in any situation that requires VM management. If you work with openstack then using RHEV would be something to look at since it does have support for it.
It might be less appropriate if you are just needing to save cost. However, using something like oVirt (similar if not the same as RHEV) would be better even though it would take a little more work to use oVirt as oVirt is not baked into the kernel.

Make way for RHEV

Overall Satisfaction with Red Hat Enterprise Virtualization