Testing FTS

This page describes the basic test setup for FTS.

Basic test deployment

The tests assume a basic installation of:

• A single FTS web-service instance
• A single transfer channel defined in the database
• A single channel agent deployed to serve that channel
• A single VO agent for dteam

The test uses the FTS CLI and should be run from the UI and worker node.

Basic test setup

Agent setup

Use yaim to configure:

• 1 "URLCOPY" channel agent for channel CERN1A-CERN1B
• 1 "VOAGENT-PYTHON" for VO dteam.

with default configuration.

Create a services.xml file to reference the certification MyProxy server and certification SRMs on sites SL3CERTTB1A and SL3CERTTB1B.

FTS web-service setup

Use yaim to configure the FTS web-service instance with default parameters. The client configuration below assumes you setup the FTS in the SL3CERTTB1A site.

Channel definition setup

This only needs to be done if the channel is not already present in the database. The example here assumes the test transfers will be running from SRMs on site SL3CERTTB1A to SRMs on site SL3CERTTB1B.

As root on the web-service node, run:

glite-transfer-channel-add CERN1A-CERN1B SL3CERTTB1A SL3CERTTB1B -f 4 -S Active -T 1

which creates a channel CERN1A-CERN1B between the two sites, with 4 concurrent file transfers with 1 TCP stream each.

Client setup

Set the gLite service discovery variables to point to the certification BDII and tell it to use the FTS server on site SL3CERTTB1A.

export LCG_GFAL_INFOSYS=lxb2017.cern.ch:2170
export GLITE_SD_PLUGIN=bdii
export GLITE_SD_SITE=SL3CERTTB1A

Running the test

Put your proxy into the certification MyProxy server.

myproxy-init -d -s lxb2020.cern.ch

Create a plain file of 4 SURL source-dest pairs, with each source referencing a file on one of the SL3CERTTB1A SRMs and each destination writing to one of the SL3CERTTB1B SRMs.

Execute:

glite-transfer-submit -f yourfile -p yourmyproxypassphrase

It'll give you back a jobID. Check periodically:

glite-transfer-status --verbose 98f4efea-c577-11da-8db9-cc65a16016cd

and you should receive a verbose status, e.g.:

Request ID:     98f4efea-c577-11da-8db9-cc65a16016cd
Status:         Active
Channel:        CERN1A-CERN1B
Client DN:      /C=CH/O=CERN/OU=GRID/CN=Gavin McCance 1222
Reason:         <None>
Submit time:    2006-04-06 14:14:01.885
Files:          50
Priority:       3
VOName:         dteam
        Done:           1
        Active:         3
        Pending:        0
        Canceled:       0
        Canceling:      0
        Failed:         0
        Finished:       0
        Submitted:      0
        Hold:           0
        Waiting:        0
        CatalogFailed:  0

without the --verbose should give you simply:

• If the job is still waiting:

glite-transfer-status 98f4efea-c577-11da-8db9-cc65a16016cd

Pending

• If the job has started running:

glite-transfer-status 98f4efea-c577-11da-8db9-cc65a16016cd

Pending

• If the job has failed partially or wholly:

glite-transfer-status 98f4efea-c577-11da-8db9-cc65a16016cd

Failed

• If the job has completed successfully:

glite-transfer-status 98f4efea-c577-11da-8db9-cc65a16016cd

Done

The individual statuses of the files that make the job may be requested:

glite-transfer-status -l --verbose 98f4efea-c577-11da-8db9-cc65a16016cd

Request ID:     98f4efea-c577-11da-8db9-cc65a16016cd
Status:         Active
Channel:        CERN1A-CERN1B
Client DN:      /C=CH/O=CERN/OU=GRID/CN=Gavin McCance 1222
Reason:         <None>
Submit time:    2006-04-06 14:14:01.885
Files:          50
Priority:       3
VOName:         dteam
        Done:           4
        Active:         0
        Pending:        0
        Canceled:       0
        Canceling:      0
        Failed:         0
        Finished:       0
        Submitted:      0
        Hold:           0
        Waiting:        0
        CatalogFailed:  0
  Source:      srm://srm.cern.ch:8443/srm/managerv1?SFN=/castor/cern.ch/grid/dteam/sc4/009/file-040.dat
  Destination: srm://dcsrm.usatlas.bnl.gov:8443/srm/managerv1?SFN=/pnfs/usatlas.bnl.gov/sc/casey/2006-04-06/file-839-6589790d-3755-4450-8111-d7f8a8acd22a.dat
  State:       Done
  Retries:     0
  Reason:      (null)
  Duration:    341

  Source:      srm://srm.cern.ch:8443/srm/managerv1?SFN=/castor/cern.ch/grid/dteam/sc4/007/file-066.dat
  Destination: srm://dcsrm.usatlas.bnl.gov:8443/srm/managerv1?SFN=/pnfs/usatlas.bnl.gov/sc/casey/2006-04-06/file-665-075d6be2-bb14-45a2-89a1-86111f5fab4b.dat
  State:       Done
  Retries:     0
  Reason:      (null)
  Duration:    286

  Source:      srm://srm.cern.ch:8443/srm/managerv1?SFN=/castor/cern.ch/grid/dteam/sc4/007/file-066.dat
  Destination: srm://dcsrm.usatlas.bnl.gov:8443/srm/managerv1?SFN=/pnfs/usatlas.bnl.gov/sc/casey/2006-04-06/file-665-075d6be2-bb14-45a2-89a1-86111f5fab4b.dat
  State:       Done
  Retries:     0
  Reason:      (null)
  Duration:    286

  Source:      srm://srm.cern.ch:8443/srm/managerv1?SFN=/castor/cern.ch/grid/dteam/sc4/007/file-066.dat
  Destination: srm://dcsrm.usatlas.bnl.gov:8443/srm/managerv1?SFN=/pnfs/usatlas.bnl.gov/sc/casey/2006-04-06/file-665-075d6be2-bb14-45a2-89a1-86111f5fab4b.dat
  State:       Done
  Retries:     0
  Reason:      (null)
  Duration:    286

and will specify the reason for any failures.

API

A perl and C API are also available.

-- GavinMcCance - 06 Apr 2006