Infrastructure Architect
Rating: 5 out of 10
IncentivizedUse Cases and Deployment Scope
Red Hat Virtualization is used to host virtual machines for our telecommunications applications.
Pros
- 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.
Cons
- 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.
Likelihood to Recommend
Red Hat Virtualization is suitable for small implementation and hosting VMs. However, when you start asking for additional features or enhancements, the engineering team is not the flexible as other engineering teams in Red Hat. It is very likely they will not accept adding features or in the best case. They wouldn't commit to a plan when it is possible to be available.
Vetted Review
8 years of experience