Project

General

Profile

SBND dCache storage » History » Version 2

Gianluca Petrillo, 09/26/2016 01:54 PM

1 1 Gianluca Petrillo
h1. SBND dCache storage
2 1 Gianluca Petrillo
3 1 Gianluca Petrillo
dCache area consists of a huge data space, made of tapes and disks.
4 1 Gianluca Petrillo
SBND owns one of each of two types of dCache areas. Each of them has room for areas owned by a single user:
5 1 Gianluca Petrillo
6 1 Gianluca Petrillo
* scratch (@/pnfs/sbnd/scratch/users/${USER}@): files in this area can be deleted automatically; you can store a grid job result there waiting to transfer it into a safe place, but don't rely on leaving your important stuff there for long
7 1 Gianluca Petrillo
* persistent (@/pnfs/sbnd/persistent/users/${USER}@): files in this area will not be deleted
8 1 Gianluca Petrillo
9 1 Gianluca Petrillo
We have a limited quota of space as well, so fill it responsibly.
10 1 Gianluca Petrillo
11 1 Gianluca Petrillo
h2. Remote access to dCache areas
12 1 Gianluca Petrillo
13 1 Gianluca Petrillo
While dCache areas may happen to be available on some local nodes (e.g., [[Computing resources#Where-to-work-interactive-nodes-GPVM|SBND GPVM's]]), in general the area is not directly reachable.
14 1 Gianluca Petrillo
We use a tool called [[ifdhc:|IFDH]] to fetch files from wherever they are. Also some code uses IFDH to fetch files: among them, LArSoft modules @CORSIKAGen@ and @GENIEGen@.
15 1 Gianluca Petrillo
16 1 Gianluca Petrillo
IFDH sometimes requires the user to be _authenticated_, which is usually achieved by a certificate.
17 2 Gianluca Petrillo
This is the [[Get a certificate proxy|same procedure]] as for getting credentials to submit jobs.