[167] in athena10
Re: Athena 10 project infrastructure status
daemon@ATHENA.MIT.EDU (ghudson@MIT.EDU)
Thu Apr 17 12:40:05 2008
Date: Thu, 17 Apr 2008 12:39:20 -0400 (EDT)
From: ghudson@MIT.EDU
Message-Id: <200804171639.m3HGdKQM025142@outgoing.mit.edu>
To: Greg Hudson <ghudson@mit.edu>
CC: athena10@mit.edu
In-reply-to: <200801231926.m0NJQ47K010216@equal-rites.mit.edu>
> Apt repository HTTP server: For simplicity, I think we'll just use
> stuff.mit.edu for development. Once things are off the ground I'll
> try to figure out what kind of hardware will be necessary for
> production.
Twice in the recent past (right now and a few days ago), stuff.mit.edu
has become very slow and needed to have httpd restarted. So I think
we want to look for another solution here. Options include:
(1) If a machine has AFS installed and stable net connectivity,
file:///afs/dev.mit.edu/system/athena10/apt works fine in
sources.list. There's a chicken-egg problem getting AFS installed, of
course.
(2) We can use a scripts.mit.edu vhost configured like debathena.
This is obviously good enough for debathena, but still relies on
SIPB-run infrastructure shared with many other uses.
(3) We can provision an ops VM and configure it to serve the apt
repository.
I think I am going to go with #3 once I can get approval, since this
is likely what the production solution will look like as well. That
will take a week or so to bring online, so I'm in the market for quick
and dirty temporary solutions if people can think of them.
