	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

To: David Alexander <alexandd@xxxxxxxx>
Subject: Re: Cosign in production at UoA and thanks
From: Wesley Craig <wes@xxxxxxxxx>
Date: Tue, 14 Jun 2005 10:31:46 -0400
Cc: Brian Hatch <bri@xxxxxxxxx>, cosign-discuss <cosign-discuss@xxxxxxxxx>
In-reply-to: <A4F385A8F4391A07DECE24FC@OHIO-LZ8JRIPC1D.ohio.edu>
References: <1118616884.4259.27.camel@brett.enarc.auckland.ac.nz> <20050612231319.GT6036@ifokr.org> <A4F385A8F4391A07DECE24FC@OHIO-LZ8JRIPC1D.ohio.edu>

On 14 Jun 2005, at 10:06, David Alexander wrote:

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.

So you're not using replication at all? Can you describe how you've deployed NFS with high-availability?

:wes

Follow-Ups:
- Re: Cosign in production at UoA and thanks
  - From: David Alexander

References:
- Cosign in production at UoA and thanks
  - From: Brett Lomas
- Re: Cosign in production at UoA and thanks
  - From: Brian Hatch
- Re: Cosign in production at UoA and thanks
  - From: David Alexander

Prev by Date: Re: Cosign in production at UoA and thanks
Next by Date: Re: Cosign in production at UoA and thanks
Previous by thread: Re: Cosign in production at UoA and thanks
Next by thread: Re: Cosign in production at UoA and thanks
Index(es):
- Date
- Thread