Setting Up a Highly Available Red Hat Enterprise Virtualization Manager (RHEV 3.5)

Latest response

What are shared directories/shared components need to be mount in order to setup HA RHEVM-3.5 ?

For RHEV 3.1, I found follows:

/usr/share/jasperreports-server-pro
/usr/share/ovirt-engine-dwh
/usr/share/ovirt-engine-reports
/usr/share/ovirt-engine
/var/lib/exports
/var/lib/ovirt-engine
/var/lib/pgsql

Available directories in RHEVM 3.5 are as follows:
/usr/share/ovirt-engine
/var/lib/exports
/var/lib/ovirt-engine
/var/lib/pgsql

Some of the shared components are missing in RHEVM-3.5. I want to know the exact details of shared directories/components to setup HA rhevm 3.5!

Attachments

su
Log in to join the conversation

Responses

Siem Korteweg's picture Guru 1450 points
2 November 2015 8:37 AM

Does the self-hosted engine setup (https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Installation_Guide/chap-The_Self-Hosted_Engine.html) meet your requirements?

su Community Member 60 points
2 November 2015 9:05 AM

By using self-hosted engine, how we can configure the shared directories/components? When primary RHEV-M went offline, secondary node should takeover the RHEV-M service. RHEV-H hosts to be accessible from secondary RHEV-M node. Therefore, how its become possible with self-hosted engine?

Siem Korteweg's picture Guru 1450 points
2 November 2015 9:27 AM

Please refer to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Installation_Guide/chap-The_Self-Hosted_Engine.html. The self-hosted setup consists of a VM (its' disk resides on a specific NFS volume) running RHEVM and several hypervisors designated to run this VM. When a hypervisor running the RHEVM fails, another hypervisor (re)runs the VM. The NFS volume of the RHEVM VM should contain all directoires required to rrun RHEVM.

You mention RHEV-H hosts and the install guide for self-hosted engine unfortunately indicates: "Red Hat Enterprise Virtualization Hypervisors and older versions of Red Hat Enterprise Linux are not recommended for use with a self-hosted engine. "

su Community Member 60 points
2 November 2015 9:50 AM

Is there any other recommended way to try so?

Siem Korteweg's picture Guru 1450 points
2 November 2015 2:21 PM

My best guess would be https://access.redhat.com/articles/216973, but you already posted in that article.

su Community Member 60 points
4 November 2015 4:31 AM

I found the possible solutions!
For RHEVM 3.0 and 3.1, we used service level clustering. This method is no longer used and has been deprecated. For RHVEM 3.3 and above, one of the following method can be used:

Self hosted Engine:
allows RHEV-M (ovirt-engine) to be installed as a special virtual machine that runs directly on the RHEV hosts that it manages. Refer more details in the following link:
https://access.redhat.com/solutions/70177

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Installation_Guide/chap-The_Self-Hosted_Engine.html

https://access.redhat.com/articles/735153

Operating system clustering :
This setup consists of 2 physical systems with 1 virtual machine that fails back and forth. Inside the virtual machine is where RHEV-M runs. Refer more details in the following link:
https://access.redhat.com/solutions/45145

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.