Transferring Datasets to UC dCache

Purpose

• Identify storage and configure if necessary resources at UC.
• Create and document subscriptions in the UC VOB DQ2 service.
• Provide access local users and the DSS project.

Storage setup at UC

• Storage systems at UC: StorageSystems (restricted to Admin-only access; To do: provide a user-page equivalent technical description of available storage resources)
• How to create and monitor subscriptions in the service.
  • How do users specify their subscriptions (provide guidance on dataset browser navigation, naming conventions, etc).
  • Submitting a subscription request to MWT2 - it should go in as a trouble ticket.
  • How do users moniter the status of their subscriptions.
• Tools for examining the LFC and checking with replicas on disk.

Accessing the datasets

• How to simply view these datasets at MWT2 (in the catalog, on the disk, etc).
• These are dCache resident - what protocols do users need from a standard Athena job?
  • Are we supporting dcap access - what changes to a standard Athena setup script are required?
  • Are we supporting srm-cp, for example, file transfers from the dCache pool to the local working directory on the compute node?
  • How do we keep users from writing data into /home/user? Where do we tell them to place their output (back in dCache? some other NFS mounted filespace?)

Performance monitoring

• Caputure I/O performance statistics:
  • DQ2 server
  • tier2-06.uchicago.edu Ganglia monitor
  • se3 storage server Ganglia monitor
• dCache read/write operations
  • Examing dCache UC_VOB: http://tier2-d1.uchicago.edu:2288/

First steps toward policy development

• We need to let users know how long they can expect their datasets to last in this area.