CAF @ CNAF How to use
by Antonio Sidoti and Stefano Belforte

Farm "opening" message

• No access to local data copies, nor to dcache
• No icaf area/service
• Main usage is for MonteCarlo production
• All output (including log files) must be directed to some location outside CNAF, this must be a node that accept incoming kerberized rcp connection (e.g. fcdflnx2/3 or fcdfsgi2, although a desktop in your INFN site is much preferrable for obvious network traffic reasons)
• CPU limits are:
  • short : 2 hours
  • medium : 6 hours
  • long : 1 day
• There is no limit on the fraction of medium/long jobs (farm is so small that makes little sense to fragment it) please do not abuse

Report problems to Antonio and/or Armando and/or Stefano and please be patient and collaborative

1. send mail to Antonio and/or Armando and/or Stefano to have your queue setup

2. if you work from a FNAL machine:

          cp ~belforte/.cafrc ~
          cp ~belforte/krb5.conf .
           add to your ~/local.login the line:
              setenv KRB5_CONFIG ${HOME}/krb5.conf
           if you use bash instead, add to ~/bash.profile the line
              export KRB5_CONFIG=${HOME}/krb5.conf
          

3. if you work from Italy:

          cp /afs/infn.it/project/cdf/cdfsoft/DotCafrc ~/.cafrc
          cp /afs/infn.it/project/cdf/cdfsoft/krb5.conf ~
          
           Then modify your .login or .bash_profile ot whatever
           your local sysman decided your local initialization
           script has to be called, so to inclue the definition of
           KRB5_CONFIG as indicated above
           

   Note that if you work from Italy and your desktop does not have the kerberos client installed, you can still work by using KRB_Lite, although this is not as conveniente and you may need more "gimnick" with kerberos conifguration

4. add to your ~/.k5login your new principal name/cdf/cnafcaf@FNAL.GOV, in order to allow the CAF@CNAF to send files (your logs e.g.) to your directory. After this your .k5login must look something like:

   belforte@FNAL.GOV
   caf/cdf/belforte@FNAL.GOV
   belforte/cdf/cnafcaf@FNAL.GOV
          

5. if you work from Italy:

   source /afs/infn.it/project/cdf/cdfsoft/cdf2.shrc

   (assuming you use bash, if you use tchs, put a "c" after the dot)

6. setup cdfsoft2 development

7. define the CAF@CNAF as your preferred CAF:
   • if you use tcsh: setenv CAF_CURRENT cnaf
   • if you bash: export CAF_CURRENT=cnaf

8. use CafGui and/or cafcom as usual, but make sure you fully specify the output node with a user@node:/directory string, you can not use the icaf: and/or scratch: shortcuts
   Example

          belforte@fcdflnx3.fnal.gov:/cdf/scratch/belforte/test.tgz
           or
          belforte@pccdf2.ts.infn.it:caf/cnaf/out/test.tgz
          

9. make sure you do not try to access any local data disk file, there are none at CNAF

10. in principle you can use rootd to access static data on fcdfsgi2 and/or FNAL's CAF static servers, in practice performance is lilkely to be awfull

11. monitor your job with the usual cafjobs/tail/top/dir/kill

12. monitor your jobs and/or the full farm from CAF@CNAF fbswww page and/or CAF@CNAF UserMonitor page

13. For examples of real analysis jobs that run on the CNAF farm, look at Antonio's Plug Electrons Analysis page

14. Send Antonio/Stefano e-mail if you find we forgot something !