[7059] in Release_7.7_team
Re: Agenda for 11/19 meeting
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Thu Nov 18 16:01:49 2010
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <8AEDB213-0F67-4824-B099-7C8987D1772B@mit.edu>
Date: Thu, 18 Nov 2010 16:01:41 -0500
Message-Id: <B33E36A6-F701-4C95-81EA-2556123446A1@mit.edu>
To: "release-team@MIT.EDU" <release-team@mit.edu>
Content-Transfer-Encoding: 8bit
Additional items:
- Realplayer (alexp)
- Release schedule (jdreed): Should we revisit the idea of only targeting LTS releases for the clusters?
On Nov 17, 2010, at 11:35 AM, Jonathan Reed wrote:
> Please send additional items to me.
>
> - Broken machines: There are a number of perpetually broken machines (macgregor-5) which have repeatedly failed re-installation. We need a good solution for these. In at least one case, the machine was re-installed by me personally and worked just fine in N42, but upon deployment to macgregor, it magically turned back into debathena-workstation.
>
> - Related to the above, "machtype -L | grep "debathena-cluster" is not an acceptable substitute for "PUBLIC=true". While there's some argument that private workstation install logs shouldn't be publicly available, w20-575-1 should, for example, always display all logs publicly, even if Debathena installation failed somehow or it got downgraded to workstation. I can think of several ways to accomplish this: Query for hesiod cluster=cluster to determine whether to view the information, or have the -cluster installation create a flag file (/etc/athena/public) in the sysroot at install time, and use that file to determine whether a machine is "public" or not. That way, debugging info will be available even for pseudo-failed installs.
>
> -Jon