Hey Sigbjorn,
I currently use a cluster of two "management nodes" with a classical
corosync/pacemaker/drbd setup which also provides DNS, DHCP, TFTP, all repositories we
need to install our VMs and the central configuration management.
We have a failover IP (and hostname) and our cluster makes sure that all
databases/services which need to be kept together are running on one host.
However, setting up something like this is a quite complex process, so having a postgresql
cluster (at least with postgres 9+) is not too difficult to set up and then having a
redundant engine cluster would be a perfect solution.
KR
Jörn
-----Original Message-----
From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf
Of Sigbjorn Lie
Sent: Mittwoch, 9. Januar 2013 12:33
To: Itamar Heim
Cc: users
Subject: Re: [Users] What do you want to see in oVirt next?
On Thu, January 3, 2013 17:08, Itamar Heim wrote:
> Hi Everyone,
>
>
> as we wrap oVirt 3.2, I wanted to check with oVirt users on what they
> find good/useful in oVirt, and what they would like to see improved/added
in coming versions?
Hi,
+1 for clustered ovirt manager for availability.
I've seen a pdf document describing how to configure Red Hat Cluster and
GFS with RHEV-M, but I feel Red Hat Cluster and GFS adds too much
complexity compared to what is required for ovirt manager.
Perhaps the use of glusterfs and keepalived (
http://www.keepalived.org/)
would be sufficient to create an easy to configure ovirt manager failover
cluster?
Regards,
Siggi
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users