# Presentation: 385689

## CDF GRID Installation Workshop

- Motivation for Workshop
- Long term computing aims
- Goal for Workshop
- Workshop overview
- Introduction to CAF/SAM/dCache
- Installation Summary
- Results of Workshop

## Motivation for Workshop

- Solution strategy:
- Accelerate Global Computing plans:
- 	50% @ FNAL & 50% outside FNAL by 05
-      (~25% outside FNAL by summer 2004)

-    Shortage Costs:
-    offline short by
-    ~0.5/1.5/1.5 Mill $ in 04/05/06

- 	 *CDF Offsite Computing Workshop*

## Plans to Integrate computing infrastructure offsite...and make them accessible for all CDF users. 

- Allow all users to generate MC on a remote site, register the produced MC with the global DH system, and have the DH system copy the produced data ``at its leisure'' to a destination of the user's choice. The user decides manually which site they want to use for their MC generation.                      (For summer 2004 conference season)
- Add storage capacity for a well defined dataset to the site, and allow all CDF users to submit jobs to analyze that dataset at that site. The user decides manually which site to submit to based on a set of web pages and alike that tell them where there dataset located, and how busy this site is at present. (For summer 2004 conference season)
- Support for fully transparent submission. The user no longer needs to pick a site, nor do they need to know which site has what data. The infrastructure software makes these decisions for them. (In summer 2005) (SAM)

- http://cdfcaf.fnal.gov/doc/dcaf/node2.html

##  
Allow all users to generate MC on a remote site, register the produced MC with the global DH system, and have the DH system copy the produced data ``at its leisure'' to a destination of the user's choice. The user decides manually which site they want to use for their MC generation.                      (For summer 2004 conference season)

Add storage capacity for a well defined dataset to the site, and allow all CDF users to submit jobs to analyze that dataset at that site. The user decides manually which site to submit to based on a set of web pages and alike that tell them where there dataset located, and how busy this site is at present. (For summer 2004 conference season) 

Support for fully transparent submission. The user no longer needs to pick a site, nor do they need to know which site has what data. The infrastructure software makes these decisions for them. (In summer 2005) 

- Allow all users to generate MC on a remote site, register the produced MC with the global DH system, and have the DH system copy the produced data ``at its leisure'' to a destination of the user's choice. The user decides manually which site they want to use for their MC generation.                      (For summer 2004 conference season)
- Add storage capacity for a well defined dataset to the site, and allow all CDF users to submit jobs to analyze that dataset at that site. The user decides manually which site to submit to based on a set of web pages and alike that tell them where there dataset located, and how busy this site is at present. (For summer 2004 conference season)
- Support for fully transparent submission. The user no longer needs to pick a site, nor do they need to know which site has what data. The infrastructure software makes these decisions for them. (In summer 2005)

- http://cdfcaf.fnal.gov/doc/dcaf/node2.html

- Goals for Workshop

-   Installation of the necessary computing infrastructure to

- Install SAM to

- Install dCache to

## What was the workshop ?

- 3 day workshop this week, ~12 hours/day.
- Participants from 11 sites incl. 3 in Asia, 4 in Europe (Karlsruhe, Glasgow, Liverpool, Oxford)
- http://cdfkits.fnal.gov/DIST/doc/DCAF/web/
- Installation of
- Day 1: CAF
- Day 2: SAM
- Day 3: dCache & Discussion of future commitments

## CAF

- Central Analysis Farm
- - Queues job
-  Sends job to available  worker nodes

- http://cdfcaf.fnal.gov/doc/dcaf/dcaf.html

*“**delivers CPU to solve the “problem””*

## SAM

- Sequential Access to Metadata
- database knowing where in world file is stored
-  file is then copied to a local area (dCache)
-  will give preference to where file obtained from/location etc.

- http://cdfkits.fnal.gov/DIST/doc/DCAF/web/Florida_workshop.html

*“**Delivers data to the CPU”*

## dCache

- File storage:
- (fast/local) data store on way to/from local CPU
- -cache between mass storage (tape) and local processing
- -temporary storage (output from one job is input to another)
- -(semi-)permanent local storage

- http://cdfkits.fnal.gov/DIST/doc/DCAF/web/resilientDcache/

- copies files to a local area
- (dCache asks nodes if each pool has the file/data – has a database to know where it is too (like SAM!), copies files to local cache? Knows where space is and allocates it (?)

- dCache – distributed Cache

## Resilient dCache

- Modified/enhanced version of the dCache software which enables it to also serve as a robust virtualized scratch space.
- This allows clients to store files, retrieve files, and otherwise manage their space within this system as they would with any normal local scratch directory.
- However, it physically stores their files on a pool of different storage elements and keeps track of where the files are stored (file metadata).
- In addition, a configurable number of copies of each file will be made on different pools to ensure fault-tolerance in file delivery against node failures. This is required to ensure that files are never lost since they are not being archived to tape in the Resilient dCache system.

- All files are disk-resident - no storage or other interaction with a tape
- Copies of files made across storage elements (pools) for redundency
- Virtualization of file space via management of metadata in PostgreSql database
- Multi-user store - quota and file/directory permission support (still needed!)

- http://cdfkits.fnal.gov/DIST/doc/DCAF/web/resilientDcache/install.html

## CAF/SAM/dCache

- CAF

- SAM

- dCache

## Results

- Problems:
- ssh/telnet/firewall

## CAF

## SAM

## dCache

## Results of Workshop

*“**Very Impressive Effort”** – Frank Wuerthwein*
- 6 sites committed for summer 2004: ~1 THz
- 		INFN,Korea,MIT,Taiwan,Toronto,UCSD
- 	(Not Liverpool !!), no UK/European institutions signed up
- Next meeting: April 1st @ Fermilab
- Aim to start using offsite sites from April 15th – Aug for summer conference data/MC
- Future:
- 	Other institutions (e.g. Karlsruhe) to sign up at later date
- 	Liverpool ?