Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Users

ldap replication in a multiple machine cluster

 

 

Linux-HA users RSS feed   Index | Next | Previous | View Threaded


bcantwell at firescope

Nov 6, 2009, 11:13 AM

Post #1 of 2 (497 views)
Permalink
ldap replication in a multiple machine cluster

I have the following environment:

2 linux machines using HA with our monitoring server (as a parent that receives data from other monitoring servers), httpd, mysql and LDAP. the vip we'll say is 10.0.2.63 and the two machines are 10.0.2.61 and 10.0.2.62.

2 other machinmes set up identically to what is explained above, but that also syncronize thier data up to our monitoring service thier child data. vip is 10.0.2.65 and machines are 10.0.2.66 and 10.0.2.67... they update thier data via 10.0.2.63

There is a possibility of multiple 'child' nodes which are ha pairs that talk to the parent vip 10.0.2.63

My ultimate question, has anyone got a solution to how we keep the ldap properly synchronized?
If the 2.66 machine has a replication agreement with 2.61 but talks via the vip, and the 2.62 machine takes over... the ldap ID on 2.62 will be different and 2.66 will have no agreement and will stop replication...

Do I have the wrong idea here or is there some NON-rocket science way of taking care of this behind the scenes simply between the two machines in the individual 2 box ha clusters?

_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


sergeyfd at gmail

Nov 6, 2009, 11:20 AM

Post #2 of 2 (459 views)
Permalink
Re: ldap replication in a multiple machine cluster [In reply to]

What do you mean by "ldap ID"? If you use syncrepl as your replication
mechanism in LDAP (supposedly you use OpenLDAP) then you just have to
make sure that your masters have the same data. There are several ways
to achieve that:

1. Shared disk storage with clustered FS. (Can be active/active DRBD
with OCFS2 ot GVS2
2. Mutlimaster mode in OpenLDAP
3. Parallel publishing into both LDAP masters by your clients.
etc...

That should guarantee that both master have the same SCN in their DBs
and shadows will be able receive updates from any master.

On Fri, Nov 6, 2009 at 12:13 PM, Cantwell, Bryan
<bcantwell [at] firescope> wrote:
> I have the following environment:
>
> 2 linux machines using HA with our monitoring server (as a parent that receives data from other monitoring servers), httpd, mysql and LDAP. the vip we'll say is 10.0.2.63 and the two machines are 10.0.2.61 and 10.0.2.62.
>
> 2 other machinmes set up identically to what is explained above, but that also syncronize thier data up to our monitoring service thier child data. vip is 10.0.2.65 and machines are 10.0.2.66 and 10.0.2.67... they update thier data via 10.0.2.63
>
> There is a possibility of multiple 'child' nodes which are ha pairs that talk to the parent vip 10.0.2.63
>
> My ultimate question, has anyone got a solution to how we keep the ldap properly synchronized?
> If the 2.66 machine has a replication agreement with 2.61 but talks via the vip, and the 2.62 machine takes over... the ldap ID on 2.62 will be different and 2.66 will have no agreement and will stop replication...
>
> Do I have the wrong idea here or is there some NON-rocket science way of taking care of this behind the scenes simply between the two machines in the individual 2 box ha clusters?
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>



--
Serge Dubrouski.
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Linux-HA users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.