Red Hat Virtualization vs. vRealize Operations

RHEV is well suited for organizations that need a cost-effective and flexible solution for their environment. As its vendor-independent software, easily install on any type of hardware. RHEV provides a GUI interface to manage the software, which makes the management of the software easier for the end-user. RHEV is best for non-production or less critical applications. RHEV can be easily integrated with other REDHAT software.

Incentivized

VRealize is well suited for an organization that is heavily invested in the VMware ecosystem. There are a ton of plugins and management packs that will allow you to integrate with just about every major area of your infrastructure whether its storage, backup, cloud, or monitoring related. It is less appropriate for a company that does not already have a financial licensing agreement with VMware already established as it can be very expensive if paid for a la carte.

Incentivized

• 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.

Incentivized

• Shows us where we can save on cost of keeping machines running, or boosting resources on VM's
• the ability to plan deployments with scenario plans that can be customized over a specific timeline
• reports that can be sent and shared with different teams or departments

Incentivized

• 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.

Incentivized

• There are less space for customization.
• Cannot use for OS monitoring.
• Some option are very complex like getting an ideal VM report.

Incentivized

The support is pretty good however some of the KB articles still reference different versions of the product so it can be hard to find answers to common questions

Incentivized

RHEV is an excellent product, includes more features, is less expensive, and has rock solid reliability and is backed with the best Red Hat Support in the industry. RHEV uses KVM under the hood which is used by all the big players in the industry (AWS, Rackspace, etc) to lower their overall costs and improve efficiency and profits and that's why RHEV is an excellent solution!

Incentivized

Much compatibility with our VMware Infrastructure.

Incentivized

• RHEV has provided a positive ROI as our customers are not experiencing as many outages during maintenances.
• We have not experienced any catastrophic failures as a result of vsphere losing connection to the ntp.
• There has been a level of stability in our environment that was not previously experienced with our previous vendor.

Incentivized

• I would not have a job without this product. It helps me become the data superstar in my organization
• The only neg is that people think I can solve all their problems with vROPs. We do not have hooks into every application so we can only provide the insight we know about
• The application is a storage hog, but if you want those metrics for that length of time then prepare to eat some disk space.

Incentivized