FW: OpenLDAP Cluster+Alteon

["Howard Chu" <hyc@highlandsun.com>]

Seems to me with an additional bit in back-glue to process referrals we
could
configure slaves to automatically forward updates (using back-ldap?) to the
right places. Just a half-backed idea, I haven't thought too hard about it
yet.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Syahrul Sazli
Shaharir
Sent: Sunday, February 10, 2002 11:32 PM
To: openldap-software@OpenLDAP.org
Subject: OpenLDAP Cluster+Alteon


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am in a process of designing a highly-available LDAP service. The goals
of the design are (1) simple (2) scalable (3) redundant (4) Use existing
Alteon load balancers, which fan out connections to one IP to multiple
IPs.

The best I can think of so far:-

         LDAP clients
              |
        ______|______
       |___Alteon____|
        |     |     |
        |     |     |
        |     |     |
        o     o     o
      ldap1 ldap2 ldap3

ldap1, ldap2, ldap3 are multi-master OpenLDAP servers. Should be most
elegant, but AFAIK multi-master support in OpenLDAP is still experimental.

Single master with chaining is not available in OpenLDAP, so the only
alternative is single master with referrals:-

         LDAP clients
           |        |
        ___|________|___
       |_____Alteon_____|
         |   |    ||||
         |   |    ||||
         |   |    ||||
         o   o    oooo
        l1  l2    slaves

l2 is cold standby master, eg l1 and l2 maintains heartbeat, if l1 down,
l2 automatically wakes up and takes over, and vice versa. Both runs slurpd
and updates all the slaves as required. Not as pretty as I want [ Masters
not scalable, and LDAP clients need to handle write referrals correctly ],
but should work.

Ideas? Past experiences? TIA! :)

- --sazli
** PGP/GnuPG Public key:- **
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4F90071F
Key fingerprint: 0E8D AFD5 7544 E481 885A  BEAA E338 B2A3 4F90 071F

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)

iD8DBQE8Z3Nm4ziyo0+QBx8RAqruAJ0XPrzdnds60o1KoIVp2HiDJL3f0wCfRELX
Q57uifN8Z68S6MV0LC+C0XI=
=w96u
-----END PGP SIGNATURE-----