[8630] in Info-AFS_Redistribution
Re: automating 'vos release'
daemon@ATHENA.MIT.EDU (Jim Barlow)
Mon Apr 16 12:08:33 2001
X-Envelope-From: jbarlow@ncsa.uiuc.edu
X-Envelope-To: <info-afs@transarc.com>
Date: Mon, 16 Apr 2001 11:01:53 -0500
From: Jim Barlow <jbarlow@ncsa.uiuc.edu>
To: info-afs@transarc.com
Message-ID: <20010416110153.A10566@osage.ncsa.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <327779890.987420775@jblaine-pc.mitre.org>; from jblaine@linus.mitre.org on Mon, Apr 16, 2001 at 11:32:55AM -0400
On Mon, Apr 16, 2001 at 11:32:55AM -0400, Jeff Blaine wrote:
> > This is going to require that we run a "vos release" on a periodic,
> > automated basis.
>
> Require?
>
> I'm against the idea in concept, but that's an opinion. Why not do
> it by hand (takes 3 seconds to type) when you know you want to
> release for sure? Anyway...
Not sure how big your cell is, or how many users you support, but doing
it by hand at many sites would not be feasible. For instance, we serve
all our web content from replicated AFS volumes. We have a couple hundered
people who can modify much of that content then need to have the modifications
pushed out to the read-only copies. If each of these users had to call
an AFS admin every time they made an update, well you get the idea. So
we release volumes at certain times and everyone knows when these volumes
will be updated. We also provide an internal web server that mounts the
read-write web tree so the web developers can look at the changes as they
make them and before they are released.
--
James J. Barlow <jbarlow@ncsa.uiuc.edu>
Senior System Engineer
National Center for Supercomputing Applications Voice : (217)244-6403
605 East Springfield Avenue Champaign, IL 61820 Cell : (217)840-0601
http://www.ncsa.uiuc.edu/People/jbarlow Fax : (217)244-1987
