[6194] in Release_7.7_team
Release Team Meeting Notes: 2/4/09
daemon@ATHENA.MIT.EDU (Bill Cattey)
Wed Feb 4 17:10:57 2009
From: Bill Cattey <wdc@MIT.EDU>
To: William Cattey <wdc@mit.edu>
Cc: release-team@mit.edu
In-Reply-To: <D8FF24DB-1D02-427A-B020-E3F620D4E9E3@mit.edu>
X-Spam-Flag: NO
X-Spam-Flag: NO
X-Spam-Score: 0.00
X-Spam-Score: -5
Content-Type: text/plain
Date: Wed, 04 Feb 2009 17:11:26 -0500
Message-Id: <1233785487.6597.64.camel@lakota.mit.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Our next meeting is scheduled next week: Tuesday 10 February at 1:30
in room TBA.
Action:
1. Check-ins on Action Items
jweiss: Can AFS janitor be co-opted to scanning for UIDs and GIDs?
Theoretically yes. Requires work to turn into a query tool.
jweiss: What is range of UIDs/GIDs assigned by moira?
Current range is between 100 and 131072
Probably should change this to 2000, which is not hard.
The expectation is that the user range between 100 and 1000 is pretty
full. So scope is somewhat big.
jdreed: What is the list of users affected by low UIDs or GIDs?
Cutoff is 2000.
jdreed: Where are we in crafting the merged Athena apt repository
write access guidelines? jdreed will ping for bullet points. tabbott
will try and send some.
jdreed: What is status of check-in with othomas on those possibly
affected by switch to bash as default shell? othomas gave green light.
jdreed sends email to zacheiss, cc ops to switch sometime before April
1.
2. Questions for team to review:
* Does Athena still want to enforce blackout dates between drop date and
the end of term for patches offered by the Athena10/debathena
repository?
For Athena 9 we had to do work to create a patch release containing
upstream OS and application updates, so the blackout period was easily
implemented.
For Athena 10 we use upstream updaters so we would have to do work to
intercept or disable upstream updates. Should we do this work?
To what extent should Athena 10 and other IS&T services sensitize
themselves to changes happening near the end of term? What is the
proper balance to strike in doing work to intervene in this area?
As time has gone on MIT has adopted a policy of adopting more upstream
and intervening less frequently.
* Meeting time
Tuesday at 1:30 every 2 weeks starting next week Tuesday Feb 10.
* Review Athena Dialup Service and options for replacing the Solaris-
based service.
What is the requirement here?
Desire to offer same dialup as cluster environment.
Very helpful to sanity check user problems on controlled
platform.
Desire to offer Linux-based dialup platform.
Long term goal to de-Support Solaris.
What are the concerns?
Workload of ops to implement/qualify the new dialup
implementation.
ASO also wants to port some Solaris-dialup-unique functionality.
Security management (expected to be more work for Linux than
Solaris.)
What are the options to move forward?
Create a couple Linux Dialup testbed VMs.
Use SIPB Linerva.
ASO needs to assess its situation.
When should there be Athena 10 Linux Dialup in place for optimal
deployment of Athena 10? When Athena 10 becomes the default. Currently
targeted for July 1.
3. Punch List to Athena 10 Early Cluster go-live:
jdreed has picked the candidate 20 systems. We need to hurry up and
deploy to them!
Punch List to Athena 10 go-live (9 items):
Comprehensive installer: thirdparty package last bit.
Create debathena-thirdparty package: On deck to deploy.
ATN-1 Improved session names: Confirm deployed?
ATN-4 Greeter cosmetics: Confirm checked-in? wdc will resolve.
ATN-13 Fix X configuration: What do we do with new X server? wdc
and amb will resolve.
New Blockers:
ATN-19 "Switch User" renders Public system un-usable. Add 2 more
places to disable it, maybe disable multiple X servers in gdm.
ATN-20 USB and CD don't work in LVM chroot. It's a hald-dbus
communication. Could go to Early with this broken, but un-desirable.
Targeting go-live of Early Cluster Tuesday Feb 10. (Will know better
Friday.)
4. Monthly Status Report
Tabled till Next week's meeting.
