Hi,
We've been running a modperl environment 'on' a NetApp since dec 1997
and would't even dare to think about going back;). We've found no
gotcha's. Iff you can afford it I can really recommend it. The way we
use it is that we store all configs, libraries and sites on the netapp.
As a front-end we have 'cheap' PC's running Linux. The disks in the PC's
are only used for the OS and temporary storage of logs, etc.
Ronald
Tim Bunce wrote:
>
> On Mon, Jan 31, 2000 at 11:16:23AM -0800, siberian wrote:
> > Hi All-
> > I am building a pretty in depth architecture for our new service
> > using ModPerl. I've done a lot of large scale/high traffic apps in modperl
> > before but never in conjunction with a network attached file server. I am
> > thinking that it would really make my life easy to have one central
> > repository of code, databases and sundry files that all the servers share
> > ( making it easy to swap out servers, add servers etc since its a central
> > file repository that everyone just hooks into ).
> >
> > My question is : Has anyone experienced any 'gotchas' in putting perl code
> > that modperl handlers use on a Network Attached file server like a network
> > appliance box ( www.netapp.com )? I am assuming that there are no real
> > issues but before i go blow a ton of cash on this thing I wanted to be
> > sure that no one had found a problem.
>
> And, just to be balanced, has anyone _not_ found any 'gotchas' and is
> enjoying life with a netapp or similar NFS file serving appliance?
>
> Tim.
--
Ronald F. Lens Tel +31 (0)20 600 5700
xxLINK Internet Services Fax +31 (0)20 600 1825
