[1895] in Release_7.7_team
cluster machines with hesiod information
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Sun Aug 1 11:40:31 1999
Message-Id: <199908011540.LAA04150@mary-kay-commandos.mit.edu>
To: release-team@MIT.EDU
Date: Sun, 01 Aug 1999 11:40:24 -0400
From: Garry Zacheiss <zacheiss@MIT.EDU>
Out of idle curiosity, I checked which public cluster machines
are in the early hesiod clusters for their platform. The results
indicate that new releases probably aren't getting as much testing while
in early release as would be desirable. Here's how things currently
stand:
early-sun4 machines:
M37-312-21.MIT.EDU
M37-312-22.MIT.EDU
M37-312-23.MIT.EDU
M37-312-24.MIT.EDU
M37-312-25.MIT.EDU
M37-312-26.MIT.EDU
M37-312-27.MIT.EDU
M37-312-28.MIT.EDU
M37-312-29.MIT.EDU
M37-312-31.MIT.EDU
M37-312-32.MIT.EDU
M37-312-33.MIT.EDU
M37-312-34.MIT.EDU
M37-312-35.MIT.EDU
M37-312-36.MIT.EDU
M37-312-37.MIT.EDU
M37-312-38.MIT.EDU
M37-312-39.MIT.EDU
M37-312-40.MIT.EDU
(all of the following are in w20):
TEST-SPARC4.MIT.EDU
TEST-SUN2.MIT.EDU
W20-575-1.MIT.EDU
total: 19 early suns in m37, 3 in w20.
early-sgi62 machines (Indys):
(located in w20):
TEST-SGI.MIT.EDU
early-sgi63 machines (O2s):
none
It seems most of our testing machines are concentrated in m37
right now, and there seemed to be consensus a while back that the m37
cluster was greatly underutilized. Would it be a good idea to spread
out the testing machines some more and place some in other clusters?
I'd suggest having some of the O2s that are being deployed soon
in w20 be put in the early-sgi63 cluster, along with some of the 4-035
O2s. Moving a couple of the Indys in 66 to the early cluster might be
interesting as well; the cluster is fairly heavily used, even in the
summer. Thoughts?
Garry
