[78] in DCNS Development
Notes from 7/24 NFS->AFS meeting
daemon@ATHENA.MIT.EDU (carla@ATHENA.MIT.EDU)
Fri Jul 26 10:18:47 1991
From: carla@ATHENA.MIT.EDU
To: release-73@ATHENA.MIT.EDU, developers@ATHENA.MIT.EDU,
Date: Fri, 26 Jul 91 10:17:42 EDT
Hi! Here are the notes from Wednesday's NFS->AFS meeting.
In attendance: Peter Roden, Jeanne Cavanaugh, Jerry Larivee, Beth
Kevles, Naomi Schmidt, Dot Bowe, Aida Liu, Carla Fermann, Anne
Salemme, Reid Pinchback, Kim Carney, Derrick Kong, Calvin Clark, Andy
Oakland, Mark Rosenstein, Richard Basch, Jeff Schiller, Chris
VanHaren, Jon Rochlis, Kevin Cunningham
Goal: start working towards closure
Peter's suggestion: No voluntary conversion campaign now. Mass
conversion as soon as reasonable after the end of the spring semester.
*Updates:
Sysdev (Mark):
"permit" command -- sent out draft proposal, received comments. Next
steps -- revised proposal, possibly design review, develop it this
fall.
making hard links work -- not worth it
ls -- don't modify, user education instead
zephyr loading -- Lucien has statistics. On average, people have 7
filsrv subs alread, adding 2 more won't be that bad. Class login is
the most heavily subbed. (Lucien will send some stats out to one of
the zephyr lists)
expunge -- Mark talked with Jonathan, and yes, there is a problem with
not knowing when the file was deleted. Can make some changes to
delete, but that would need to be in a release for it to be effective,
Richard believes it might be easy to do for this release, he thinks.
moira -- has worked up a design, will circulate. A couple of weeks'
worth of work.
afs command server -- discussed doing this through moira instead
daily disk log -- fairly trivial
User Services: (Carla)
hesiod mixup -- can automate it so that won't happen. If the volume
create fails, log it as a critical error, and create the volume on a
different server.
moving lockers -- tar won't copy acl's, but Jay has a shellscript to
do it.
documentation
- if not voluntary, don't need "motivational" doc
- filesystems in general
- NFS-> AFS conversion doc & posters
- system manager type things
- man pages
- stock answers
what about "unadvertized" voluntary conversion? (non-staff people who
want to move)? Once the tools are set, user account should start
handling these.
Some things will stay NFS -- departmental servers, bitbucket,
non-athena servers
What about living groups with slow network connections, can't use AFS?
We have this problem now; if you're at the other end of a slow link,
it's painfully slow. 7.3 may help this. Will we allow voluntary
staying with NFS?
Operations/migration: (Anne)
- goals haven't changed
- wrote up preparation plan (was mailed out)
- with User Accounts and Faculty Liaisons, identify "complicated"
lockers (in terms of acl's etc)
================
Peter will put conclusings in writing. Shooting for involuntary
conversion sometime next June. Reconvene April '92?
Carla
