[1317] in SIPB-AFS-requests
*-mainters
daemon@ATHENA.MIT.EDU (Matt Braun)
Fri Apr 15 12:53:16 1994
To: sipb-afsreq@MIT.EDU, charon-maintainers@MIT.EDU, rtfm-maintainers@MIT.EDU,
webmaster@MIT.EDU, usenet@MIT.EDU
Date: Fri, 15 Apr 94 12:51:02 EDT
From: Matt Braun <mhbraun@MIT.EDU>
It seems that we will need to get together in the near future to discuss the
future of our server machines.
My understanding is that we are getting 3 ss10's (not an additional maxine)
and given back rosebud and the ds5000.200, and a ds3100
I Have 2 proposed schemes for migration:
1)
bed -> ss10 (pumped) (ds5000.200 goes away)
rtfm -> ss10 (ds5000.25 freed)
beacon -> ss10 (ds5000.25 freed)
and then
rosebud -> old beacon (ds5000.25)
charon (discuss, bitnet, lnf, logins, etc) -> old rtfm (ds5000.25)
www -> moves in with rtfm.
rationale: having a ds5000.25 available to be used to test out new services
would be a win. Since the it is pretty clear that IS is not going to stick
with SunOS, then there is no advantage in using the 'new platform' and a lot
of advantage in using one we are familar with. Although rtfm uses a lot of
cycles, the controls exist to cap the usage. This way, the services that
largely server the outside world are together so they do not interfere with
inside MIT
2)
(my second choice)
having www be on the maxine and put 'charon' on with rtfm.
Comments ?
Matt
