welcome: please sign in

The following 358 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
able   add   address   addsite   Admin   Administration   afs   afs1   afs2   after   all   All   Always   always   an   and   Andrew   another   apply   approximately   April   are   as   at   Attach   away   backing   be   because   been   before   between   bin   bos   Bos   both   but   by   can   case   Category   caution   cell   Cell   cellservdb   central   changeaddr   chmod   chown   client   clients   cluster   comes   command   common   completely   Config   configuration   confuses   consists   contain   Contents   continuity   Copy   correctly   Create   create   cryptically   Currently   Daemon   data   databases   dbserver   deb   debian   declaration   deleuze   determines   different   dig   directory   Do   do   doesn   domtool   done   down   dpkg   due   each   Each   Edit   elsewhere   Ensure   ensure   ensuring   entries   essentially   etc   even   exactly   example   Execute   existing   Existing   fail   field   File   file   files   fileserver   fileservers   find   five   for   format   formats   from   full   Furthermore   generating   generic   gov   grand   greater   has   hash   have   hcoop   Here   Historical   historical   Hostname   hostname   html   https   id   If   in   indicates   info   information   Install   installed   is   it   It   its   keep   kept   Key   know   kprop   Krunk   krunk   let   like   line   lines   list   List   listed   lists   listvol   ll   ln   logs   machine   machines   Machines   mail   make   mark   mention   mentioned   minimum   minutes   mkdir   modified   more   most   much   must   mysteriously   name   necessary   needed   Needs   needs   net   new   New   newserver   next   nice   not   note   Note   Now   numeric   Of   of   often   ok   old   oldaddr   On   on   one   openafs   operate   or   order   org   other   our   Outdated   ovaloffice   Packages   peer   people   performed   performing   periodically   permissions   pipermail   places   possible   practice   previous   previously   priority   published   raid   readonly   really   reasons   recognize   record   records   Records   rejoin   release   Relink   reload   remove   Remove   removes   removing   replicate   Replicate   replicated   required   resides   Resolves   Restart   restart   restarting   restrictive   reverse   root   Run   safe   same   scp   scripts   Serv   Server   server   Servers   servers   service   Set   setup   Setup   sf   short   shorter   should   shutdown   sign   simplify   simultaneously   So   so   some   start   starting   stay   steps   storage   store   story   strange   superseded   supposed   sure   symlink   symlinking   sync   System   Table   tabs   tasks   tell   than   that   The   the   their   them   These   these   they   this   This   time   to   To   touch   Unfortunately   Up   Update   use   User   usually   versa   very   vice   vicepa   volname   volume   Volumes   volumes   vos   wait   want   way   We   we   were   whatever   wheel   when   which   whitehouse   whose   widely   wiki   will   with   work   Work   works   worst   would   You   you  

Clear message
Edit

SetupNewAfsServer

This has been superseded by DaemonAdmin/AndrewFileSystem

These steps are listed in approximately the order in which they should be performed, after performing all of the "generic" steps in SetupNewMachines.

Contents

  1. Update Existing Machines
    1. Update AFSDB DNS Records
    2. Update CellServDB on AFS Servers
    3. Restart All AFS Servers
  2. Set Up New AFS Server
    1. Ensure Hostname Resolves
    2. Copy CellServDB, UserList, KeyFile, BosConfig, ThisCell
    3. Relink CellServDB and ThisCell
    4. Create /vicepa
    5. Install Debian Packages
  3. Replicate Volumes
  4. Remove AFS server
  5. To Do

Update Existing Machines

Update AFSDB DNS Records

You'll want to add a new AFSDB record for the new server. Note that the numeric field in an AFSDB record must always be "1" -- it is not a priority like in MX records! The order of the records determines their priority (not like SRV records).

Update CellServDB on AFS Servers

On all existing AFS servers, add the IP address for the new machine to /etc/openafs/server/CellServDB (this should be a symlink to /etc/openafs/CellServDB but not vice-versa). The format of this file is very strange, and often confuses people:

  1. A line starting with a ">" (greater-than sign) indicates the start of the declaration of the servers for a cell. The name of the cell comes after the greater-than.

  2. All lines between the previous line and the next line starting with a greater-than sign are servers for the previously mentioned cell. Each of these lines consists of an IP address, one or more tabs, a hash mark, and the hostname of the server.

Here is an example: 

>hcoop.net
1.1.1.1        #afs1.hcoop.net
2.2.2.2        #afs2.hcoop.net
>whitehouse.gov
0.0.0.0        #ovaloffice.whitehouse.gov

Restart All AFS Servers

Now, restart each of the existing AFS servers, one at a time, so they reload their CellServDB files. To completely ensure continuity of service, always wait a full five minutes after restarting one server before restarting the next one (five minutes is the worst-case time needed for AFS peer servers to "recognize" each other and rejoin the cluster; in practice the time required is usually much, much shorter).

Unfortunately this really is necessary.

Set Up New AFS Server

Ensure Hostname Resolves

Execute this command, and make sure it works. If it doesn't, the AFS server will fail cryptically and mysteriously. 

dig +short `hostname`

Copy CellServDB, UserList, KeyFile, BosConfig, ThisCell

Copy the CellServDB, UserList, KeyFile, and BosConfig from an existing AFS server: 

mkdir -p /etc/openafs/server/
scp deleuze.hcoop.net:/etc/openafs/server/UserList /etc/openafs/server/
scp deleuze.hcoop.net:/etc/openafs/server/KeyFile /etc/openafs/server/
chown root:wheel /etc/openafs/server/KeyFile
chmod o-r /etc/openafs/server/KeyFile
scp deleuze.hcoop.net:/etc/openafs/CellServDB /etc/openafs/CellServDB
scp deleuze.hcoop.net:/etc/openafs/BosConfig /etc/openafs/BosConfig

The AFS client and server (which can both be simultaneously installed on the same machine) keep their CellServDB's in different places, for historical reasons. We can simplify our setup by symlinking the server's to the client's (the reverse will not work due to restrictive permissions on /etc/openafs/server/): 

mkdir -p /etc/openafs/server/
ln -sf /etc/openafs/CellServDB /etc/openafs/server/CellServDB
ln -sf /etc/openafs/ThisCell   /etc/openafs/server/ThisCell

Create /vicepa

The AFS server will store its files in /vicepa. So, you should create that directory, ensuring it resides on whatever storage (raid, etc) you want to use for AFS backing. Furthermore, you must let AFS know that it is safe to use it: 

touch /vicepa/AlwaysAttach

Install Debian Packages

dpkg -i /afs/hcoop.net/common/debian/openafs/1.4.6/openafs-{fileserver,dbserver}*.deb

Replicate Volumes

We want most of our readonly volumes to be replicated as widely as possible. So, for each readonly volume, you should: 

vos addsite newserver.hcoop.net /vicepa volname
vos release volname

Currently, the minimum of volumes you should replicate are: 

common.bin
common.databases
common.logs
old
root.afs
root.cell

Remove AFS server

Here's a list of tasks that were done when we were removing Krunk:

To Do

The information in CellServDB needs to stay in sync with the AFSDB DNS entries -- they both contain essentially exactly the same data in different formats. Unfortunately AFS can't be modified to "do away with" the CellServDB file because the AFS fileservers are supposed to be able to operate correctly even when DNS is down (clients are another story). So, it would be nice to have some way of generating the CellServDB from the AFSDB records periodically.

CategorySystemAdministration CategoryNeedsWork CategoryOutdated CategoryHistorical

SetupNewAfsServer (last edited 2018-04-16 05:00:21 by ClintonEbadi)