CoSign: Collaborative Single Sign-On  
AnnouncementsDiscussion
 

cosign-discuss at umich.edu
general discussion of cosign development and deployment
 

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cosign in production at UoA and thanks




We implemented Cosign behind a F5 BigIP load balancer. Our short-term solution uses NFS as a shared file store between blades. Although we have a high availability architecture for NFS, we are concerned with the response time of NFS under load. In the future, we would like to replace the file reads and writes with Oracle database calls.


Dave


--On Sunday, June 12, 2005 4:13 PM -0700 Brian Hatch <bri@xxxxxxxxx> wrote:




Our central servers, consisting of two machines behind a foundry have
been preforming brilliantly.

I would love to hear exactly how you've set up your load balancing.


Our current needs don't require it, but I'll be rolling it out on the
BigIPs when I have a chance.  Given Cosign's... unique... architecture,
I'm curious which way you set things up and how it's working for you.



--
Brian Hatch                  A farm can produce produce.
   Systems and
   Security Engineer
http://www.ifokr.org/bri/

Every message PGP signed





 
Copyright © 2002 - 2004 Regents of the University of Michigan :  Page last updated 15-December-2010