Thanks Corey. That's exactly what I want. At least 2 servers doing replication and the failover part is just moving the virtual IP to the slave server.. Thanks.. -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Kovacs, Corey J. Sent: Thursday, March 09, 2006 8:25 AM To: linux clustering Subject: RE: RHEL4.0 CS and Ldap Dalton, I figured as much and you could indeed use the CS portion to do what Heartbeat does. I do that same thing on RHEL3CS. It's the replication part that doesn't fall into the clusterring category, that's all. The cluster serverices (resource manager) does, in effect, what hearbeat does tho so you can either have a single instence bounce aroung from node to node as needed, or you could have a master + replicas all running at the same time (with differnet data stores) and not have to worry about the service failing over, just flip IP address, which is what it sounds like you are doing already. For better performance tho, if that's needed, you'll prolly want the LVS (piranha) solution. Good luck Corey -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Dalton, Maurice Sent: Thursday, March 09, 2006 9:17 AM To: linux clustering Subject: RE: RHEL4.0 CS and Ldap I am currently using Heartbeat to solve my need for Highly Available Ldap servers. I was just trying to figure another way to provide HA, replication with RHEL4.0 CS. It would be nice to build a RHEL4.0 CS service for ldap that would cover all of my requirements. Just a thought. Thanks for the replies... -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Kovacs, Corey J. Sent: Thursday, March 09, 2006 8:08 AM To: linux clustering Subject: RE: RHEL4.0 CS and Ldap You might be able to, but it's not really cluster related. You'll get better information on the openldap lists. Cheers. Corey -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Baesso Mirko Sent: Thursday, March 09, 2006 9:00 AM To: linux clustering Subject: R: RHEL4.0 CS and Ldap Sorry but i try to use sync-replica either then slurpd on openldap 2.3, can i setup a multi-master environment? Baesso Mirko - System Engineer KSolutions.S.p.A. Via Lenin 132/26 56017 S.Martino Ulmiano (PI) - Italy tel.+ 39 0 50 898369 fax. + 39 0 50 861200 baesso@xxxxxxxxxxxxx http//www.ksolutions.it -----Messaggio originale----- Da: Kovacs, Corey J. [mailto:cjk@xxxxxxxxxx] Inviato: giovedì 9 marzo 2006 14.43 A: linux clustering Oggetto: RE: RHEL4.0 CS and Ldap Multi master LDAP is not all that it's cracked up to be. There are few benefits in being able to write to different servers. The problem is that like many things, the rule is "Last write wins". Writing in LDAP dirs is not something that is "typically" done in high volumes anyway, but reading is. If you just need to load balance traffic, then you might look into an LVS implementation. That way you can set up several replicas and spread the load across them. If your Master gets blown away, you can promote of the replicas to a master.. Just takes some manual intervention. Just my two cents... Corey -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Nick Burrett Sent: Thursday, March 09, 2006 4:49 AM To: linux clustering Subject: Re: RHEL4.0 CS and Ldap Rainer Duffner wrote: > Lon Hohberger wrote: > >> On Wed, 2006-03-08 at 12:43 -0600, Dalton, Maurice wrote: >> >> >>> Is there a way to create an Ldap cluster that can do replication >>> with RHEL 4.0 CS? >>> >> >> >> For some reason, I though OpenLDAP had built-in replication? >> >> > > > Not multi-master (which I assume is what the original poster wants). > > http://www.redhat.com/en_us/USA/home/solutions/directoryserver/ > > exists for a reason... As I understand it, multi-master can be accomplished in OpenLDAP 2.3 using sync-replication between the two nodes. This is not true multi-master, but the effect is near-enough. Regards, Nick. -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
