gLite UI Install - SLC 3.0, gLite 3.0

The FTS transfer tools come as a part of the gLite UI install.  The quickest way to install gLite is the following:

• Create a file named glite-rhel30.list in /etc/apt/sources.list.d.  It only needs one line:
  

  rpm http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/ rhel30 externals Release3.0 updates

• Update your apt database:
  

  apt-get update

• Now, apt-get the required packages:
  

  apt-get install glite-ui-config

• The glite install requires quite a bit of configuring.  Copy the following files from /opt/glite/etc/config/templates to /opt/glite/etc/config:
  
  • glite-file-transfer-service-client.cfg.xml
  • glite-global.cfg.xml
  • glite-lfc-client.cfg.xml
  • glite-rgma-client.cfg.xml
  • glite-rgma-common.cfg.xml
  • glite-security-utils.cfg.xml
  • glite-service-discovery.cfg.xml
  • glite-ui.cfg.xml
  You'll need to edit the files, which you obviously don't want to do.  Instead, download my defaults, and edit a couple of necessary lines
• Edit the following lines:
• glite-global.cfg.xml: Fix value of JAVA_HOME to reflect your site's java install.
• glite-rgma-common.cfg.xml: Change rgma.server.hostname to something having the same domain name as your site; it doesn't need to be a valid host, as we aren't using this component right now.
• glite-service-discovery.cfg.xml: Change the value of service-discovery.site to reflect your hostname.
• Run the configuration script (make sure there are no "failed" components):
  

  /opt/glite/etc/config/scripts/glite-ui-config.py

• Copy the environment script into the default profile, if desired:
  

  cp /etc/glite/profile.d/glite_setenv.* /etc/profile.d/

• Source the configuration script:
  

  source /etc/profile.d/glite_setenv.sh

  (This will be done the next time you log in automatically).  Or,
  

  source /etc/glite/profile.d/glite_setenv.sh

gLite UI Install - SLC4, gLite 3.1

These directions have not yet been completed.

Using FTS in a few easy steps:

1. FTS uses a special myproxy server.  Upload your proxy to myproxy.cern.ch:
   

   $ myproxy-init -d -s myproxy-fts.cern.ch
   			Your identity: [yourDN]
   			Enter GRID pass phrase for this identity:
   			Creating proxy .................................................. Done
   			Proxy Verify OK
   			Your proxy is valid until: [date]
   			Enter MyProxy pass phrase:
   	 		Verifying password - Enter MyProxy pass phrase:
   			A proxy valid for [#hours] hours ([#days] days) for user [yourDN] now exists on myproxy-fts.cern.ch.
   

2. Submit a transfer job using glite-transfer-submit, taking note of the returned job UUID:
   

   glite-transfer-submit -s https://cmssrv29.fnal.gov:8443/glite-data-transfer-fts/services/FileTransfer srm://cmssrm.fnal.gov:8443/srm/managerv1?SFN=/9/LoadTest/FTS/TESTFILE srm://thpc-1.unl.edu:8443/srm/managerv1?SFN=/pnfs/unl.edu/data4/test/TESTFILE.FTS.fromfnal.oct2.4

3. Check on the status periodically using glite-transfer-status (passing the UUID from the previous step); you want the transfer to eventually go to "Done", not "Failed".
   

   glite-transfer-status -s https://cmssrv29.fnal.gov:8443/glite-data-transfer-fts/services/FileTransfer 3122856b-53ba-11db-8448-f38cec2f7683

4. In order to get a bit more data about what happened to a transfer, use the "-l" option for the glite-transfer-status:
   

   [osg-test2] /home/brian > glite-transfer-status -s https://cmssrv29.fnal.gov:8443/glite-data-transfer-fts/services/FileTransfer 3122856b-53ba-11db-8448-f38cec2f7683 -l
   Done
     Source:      srm://cmssrm.fnal.gov:8443/srm/managerv1?SFN=/9/LoadTest/FTS/TESTFILE
     Destination: srm://thpc-1.unl.edu:8443/srm/managerv1?SFN=/pnfs/unl.edu/data4/test/TESTFILE.FTS.fromfnal.oct2.4
     State:       Done
     Retries:     0
     Reason:      (null)
     Duration:    13

Quickly setting up FTS in Phedex

In Phedex, using FTS is very similar to using SRM.  Of course, the prerequisite to using this is having FTS successfully installed and testing it as in the previous section.  Here's the FileDownload configuration I use:

### AGENT LABEL=download-master-fts PROGRAM=Toolkit/Transfer/FileDownload DEFAULT=on
 -db              ${PHEDEX_DBPARAM}
 -nodes           ${PHEDEX_NODE}_Buffer
 -storagemap      ${PHEDEX_STORAGEMAP}
 -delete          ${PHEDEX_CONF}/FileDownloadDelete
 -validate        ${PHEDEX_CONF}/FileDownloadVerify
 -backend         SRM
 -command         ${PHEDEX_SCRIPTS}/Utilities/ftscp,-passfile=${PHEDEX_PROTECTED}/ftspass,-server=${PHEDEX_FTS_SERVER}
 -timeout         12600 # 3h30

The difference here is only in the command option.  It calls the ftscp program; in order to use it, you need to have a file (called ftspass in this example) which contains the password you used for the myproxy.cern.ch server referenced above.  You will need to chmod ftspass to readonly (chmod 600 ftspass) for ftscp to accept it. Finally, you need to reference the FTS server you will be using.  For USCMS sites, the FTS server is currently:

PHEDEX_FTS_SERVER=https://cmssrv29.fnal.gov:8443/glite-data-transfer-fts/services/FileTransfer

Start the download-master-fts script and stop the current download-master script.  Watch the logfiles, and make sure there aren't any problems.  Good luck!