A lot of this should translate to other distributions as well, but YMMV.
This section is almost definately OS/Distro independant.
AFS depends on a working Kerberos installation. Refer to KerberosNotes.
Though AFS seems fairly filesystem independant, it really prefers having a seperate partition for your AFS cell. Apparently it requires a different fsck(8) for magical reasons too, so its probably best to follow this. Put your first partition on /vicepa, and your second on /vicepb, and so on. You can also use the namei backend which is slow, but is FS/OS independant, provided you can do normal filesystem stuff.
Some people report AFS required their server's hostname to resolve properly via DNS, or they'd get weird problems for no apparent reason. This does not seem to be consistent and might be Kerberos issue.
Make sure AFS likes your kernel before continuing, or else things may fail for no good reason. Some people report problems with AFS on kernel versions others have no trouble with, so check your own setup.
The pertinent Debian packages are
Your cellname should be your lower-case DNS name, eg element.tla. Your DBServer for AFS should be the DNS name of the machine you are installing on currently.
kadmin.local -e des-cbc-crc:v4
addprinc -randkey afs ktadd -k /tmp/afs.keytab afs quit
kadmin.local
addprinc root
(enter passwords)
quit
asetkey add 3 /tmp/afs.keytab afs
Adding a princ for root is probaby a bad idea. The "Kerberos Way" is to have user/instance, eg joeshmoe/admin, known to AFS as joeshmoe.admin.
You can later add /vicepb, /vicepc etc.
Make sure /etc/openafs/!ThisCell? looks something like
element.tla
and /etc/openafs/!CellServDb? resembles
element.tla # cell
10.66.1.101 # afs.element.tla
At this point, make sure you have compiled the OpenAFS modules for your kernel. If you build a new kernel at the same time, reboot now so you can get these modules installed properly.
One page links to AFSNotes: