PPS configuration for ATLAS

In order for ATLAS to perform first tests with the SRM v2.2 test endpoints the following requirements should be satisfied:

1. Provide both or only one of the following storage classes:
   • REPLICA-ONLINE (Tape0Disk1)
   • CUSTODIAL-NEARLINE (Tape1Disk0)
2. Define the following space token descriptions:
   • TAPE for the CUSTODIAL-NEARLINE storage class
   • DISK for the REPLICA-ONLINE storage class
3. Provide resources such that a transfer sustain rate of 40MB/sec is supported by a single Tier-1. The resources provided so far are:

         SITE        DISK(!T0D1)      TAPE(!T1D0)
         NDGF        1.5TB
         IN2P3
         FZK
         CNAF        100GB
         BNL
   

4. Make available an ATLAS specific path (ex. /atlas). ATLAS will then create further paths specifying the desired space token, provided that tokens will be decided somewhere in some top levels and will not change for data stored in the leaves of that top directory.
5. Enable the following group/roles to reserve space:
   • /atlas/Role=production
   • /atlas/soft-valid/Role=production
     Please note that in the case of DPM the syntax to use for the group is "atlas/Role=production" (without the leading slash) as stored in the cns_db.Cns_groupinfo table.
6. Publish the test SRM v2.2 endpoint in the production BDII.
7. Publish in the GLUE schema the ATLAS specific root path (GlueSAPath)
8. Publish the space token descriptions (GlueSATag) and the storage classes supported by your site.
9. Publish the size made available for ATLAS and for a particular storage class/space token description at your site.

For publishing information in the GLUE schema, you can find an example here.
As a first step ATLAS will try to move data from CERN CASTOR2 SRM v1 instance to SRM v2 endpoints in the PPS testbed using FTS 2.0.

-- Flavia Donno - 06 September 2007