Tom and Richard have a page describing current NFS disk usage:

NFS/GPFS and Xroot Disk Assets

Suggestion: We should create a directory structure something like this:

/nfs/slac/g/glast/ground/links/logfiles/PII/MC-tasks
                                           /LIProc
                                           /ASP
                                           /RSP
                              /documentation/Alarms
                              /reports/MootConfig
                                       ISOC
                              /data/ASP/FlareAdvocate
                                       /GRBMonitoring
                                       README <- telling people not to put large files here
                              /users
                              /etc...etc

These can all be links to whatever NFS volume seems appropriate right now, we should only ever access these directories via the links above, never by their explicit /uNN names.

We can then move things for load balancing or because disks fill up, or because we change our mind about whether things need to be FTP accessible or not or because the disks have become too old without changing any code. We will not have to spend time worrying about which NFS volume to use because for the most part it will not matter.

Notes/Questions

  • Should links be in NFS or AFS
  • We should create an FTP link to the top level of the structure.
    • We can control FTP access by removing world read access to the directories
      • NFS groups or AFS ACLs?
    • We should remove most of the ogl /glast.uNN/ links from FTP
  • Tom asks how we will handle eventually spanning multiple disks
  • No labels