I am looking for recommendations from the CAS community on the best practices you have found for LDAP and MySQL redundancy.
A quick background of our current setup. I have two CAS nodes behind a load balancer that is using memcache to share the ticket registry. One Oracle database that is backing CAS for auditing, service registry, and a couple other home grown checks that are made within the web flow of CAS. We do not like the single point of failure in the current setup. When we upgrade to the latest version of CAS in the very near future we were considering having each CAS node host its own LDAP and MySQL database to support it. Therefore if a CAS node were to go down, it will not impact the other node(s). The problem is if we are to add a service it would then need to replicate to each node in the cluster. The same goes with the LDAP store. If we added a user it will need to be added to all tiers. I was curious how some other people tackled this. Or if you were able successfully implement a reliable Master-Master or Master-Slave replication solution with LDAP and MySQL. Or would you recommend having one LDAP and MySQL server support all of nodes of the CAS cluster. Thanks, -Jeremy ________________________ Jeremy Wickham Systems Analyst Mississippi State University [email protected]<mailto:[email protected]> -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
