1. Computing Sciences Directorate, L B N L 1 SC 2003 Storage Resource Managers: Essential Components for the Grid Arie Shoshani Staff: Alex Sim, Junmin Gu, Alex Romosan, Viji Natarajan Scientific Data Management Group Lawrence Berkeley National Laboratory http://sdm.lbl.gov/srm

2. Computing Sciences Directorate, L B N L 2 SC 2003 Outline What are Storage Resource Managers - MotivationWhat are Storage Resource Managers - Motivation General Analysis Scenario and the use of SRMsGeneral Analysis Scenario and the use of SRMs SRM functionalitySRM functionality Real examples of working SRMsReal examples of working SRMs Advantages of using SRMsAdvantages of using SRMs Conclusions and Future WorkConclusions and Future Work

3. Computing Sciences Directorate, L B N L 3 SC 2003Motivation Grid architecture needs to include reservation & scheduling of:Grid architecture needs to include reservation & scheduling of: Compute resources Storage resources Network resources Storage Resource Managers (SRMs) role in the data grid architectureStorage Resource Managers (SRMs) role in the data grid architecture Shared storage resource allocation & scheduling Especially important for data intensive applications Often files are archived on a mass storage system (MSS) large scientific collaborations (100’s of clients) – opportunities for file sharing File replication and caching may be used Need to support non-blocking (asynchronous) requests

4. Computing Sciences Directorate, L B N L 4 SC 2003 Types of SRMs Types of storage resource managersTypes of storage resource managers Disk Resource Manager (DRM) Manages one or more disk resources Tape Resource Manager (TRM) Manages access to a tertiary storage system (e.g. HPSS) Hierarchical Resource Manager (HRM=TRM + DRM) An SRM that stages files from tertiary storage into its disk cache SRMs and File transfersSRMs and File transfers SRMs DO NOT perform file transfer SRMs DO invoke file transfer service if needed (GridFTP, FTP, HTTP, …) SRMs DO monitor transfers and recover from failures TRM: from/to MSS DRM: from/to network

5. Computing Sciences Directorate, L B N L 5 SC 2003 A multi-file request to a Disk Resource Manager... client File Transfer Service Disk Cache file transfer requests network DRM Disk Cache... Disk Cache File Transfer Service multi-file request file access client Tape System Client-SRM Communication

6. Computing Sciences Directorate, L B N L 6 SC 2003 Accessing Remote Storage Resource Managers Tape System Disk Cache file transfer requests network DRM Disk Cache... Disk Cache multi-file request file access... client DRMHRM SRM-SRM Communication

7. Computing Sciences Directorate, L B N L 7 SC 2003 General Analysis Scenario MSS Request Executer Storage Resource Manager Metadata catalog Replica catalog Network Weather Service logical query network client... Request Interpreter request planning A set of logical files Execution plan and site-specific files Client’s site... Disk Cache Disk Cache Compute Engine Disk Cache Compute Resource Manager Storage Resource Manager Compute Engine Disk Cache Requests for data placement and remote computation Site 2 Site 1 Site N Storage Resource Manager Storage Resource Manager Compute Resource Manager result files Execution DAG : Uniform SRM Interface : Uniform SRM Interface

8. Computing Sciences Directorate, L B N L 8 SC 2003 SRM is a Service (OGSA, CORBA, C++, Java, …) SRM functionalitySRM functionality Manage space Negotiate and assign space to users Manage “lifetime” of spaces Manage files on behalf of a user Pin files in storage till they are released Manage “lifetime” of files Manage action when pins expire (depends on file types) Manage file sharing Policies on what should reside on a storage resource at any one time Policies on what to evict when space is needed Get files from remote locations when necessary Purpose: to simplify client’s task Manage multi-file requests A brokering function: queue file requests, pre-stage when possible Provide grid access to/from mass storage systems HPSS (LBNL, ORNL, BNL), Enstore (Fermi), JasMINE (Jlab), Castor (CERN), MSS (NCAR), …

9. Computing Sciences Directorate, L B N L 9 SC 2003 SRM works with other SRMs as well as legacy systems by using GridFTP DRM Disk Cache Disk Cache Disk Cache Disk Cache Berkeley ChicagoLivermore HRMGridFTP FTP Disk Cache Request Interpreter Request Manager DRM GridFTP client server Logical Request Data Path Control path Legend:

10. Computing Sciences Directorate, L B N L 10 SC 2003 Tomcat servlet engine Tomcat servlet engine MCS Metadata Cataloguing Services MCS Metadata Cataloguing Services RLS Replica Location Services RLS Replica Location Services SOAP RMI MyProxy server MyProxy server MCS client RLS client MyProxy client GRAM gatekeeper GRAM gatekeeper CAS Community Authorization Services CAS Community Authorization Services CAS client NCAR-MSS Mass Storage System HPSS High Performance Storage System HPSS High Performance Storage System DRM Storage Resource Management DRM Storage Resource Management HRM Storage Resource Management HRM Storage Resource Management HRM Storage Resource Management HRM Storage Resource Management HRM Storage Resource Management HRM Storage Resource Management gridFTP server gridFTP server gridFTP server gridFTP server gridFTP server gridFTP server gridFTP server gridFTP server openDAPg server openDAPg server gridFTP Striped server gridFTP Striped server LBNL LLNL USC-ISI NCAR ORNL ANL DRM Storage Resource Management DRM Storage Resource Management disk Earth System Grid

11. Computing Sciences Directorate, L B N L 11 SC 2003 Uniformity of Interface  Compatibility of SRMs SRM Enstore JASMine Client USER/APPLICATIONS Grid Middleware SRM DCache SRM CASTOR SRM Disk Cache

12. Computing Sciences Directorate, L B N L 12 SC 2003 Where do SRMs belong in the Grid architecture?

13. Computing Sciences Directorate, L B N L 13 SC 2003 SRMs provide a brokering service by supporting multi-file requests

14. Computing Sciences Directorate, L B N L 14 SC 2003 DataMover: SRMs use in ESG and PPDG for Robust Muti-file replication for Robust Muti-file replication HRM-COPY (thousands of files) SRM-GET (one file at a time) GridFTP GET (pull mode) stage files archive files Network transfer Get list of files From directory Recovers from file transfer failures Anywhere Disk Cache DataMover (Command-line Interface) HRM (performs writes) LBNL/ ORNL Disk Cache HRM (performs reads) NCAR NCAR-MSS Recovers from staging failures Recovers from archiving failures Web-based File Monitoring Tool

15. Computing Sciences Directorate, L B N L 15 SC 2003 Concepts: Types of Files Volatile: temporary files with a lifetime guaranteeVolatile: temporary files with a lifetime guarantee Files are “pinned” and “released” Files can be removed by SRM when released or when lifetime expires PermanentPermanent No lifetime Files can only be removed by creator (owner) Durable: files with a lifetime that CANNOT be removed by SRMDurable: files with a lifetime that CANNOT be removed by SRM Files are “pinned” and “released” Files can only be removed by creator (owner) If lifetime expires – invoke administrative action (e.g. notify owner, archive and release)

16. Computing Sciences Directorate, L B N L 16 SC 2003 Concepts: Types of Spaces TypesTypes Volatile Space can be reclaimed by SRM when lifetime expires durable Space can be reclaimed by SRM only if it does NOT contain files Can choose to archive files and release space Permanent Space can only be released by owner or administrator Assignment of files to spacesAssignment of files to spaces Files can only be assigned to spaces of the same type Spaces can be reservedSpaces can be reserved No limit on number of spaces Space reference handle is returned to client Total space of each type are subject to SRM and/or VO policies Default spacesDefault spaces Files can be put into SRM spaces without explicit reservation Defaults are not visible to client Compacting spaceCompacting space Release all unused space – space that has no files or files whose lifetime expired

17. Computing Sciences Directorate, L B N L 17 SC 2003 Concepts: Directory Management Usual unix semanticsUsual unix semantics srmLs, srmMkdir, srmMv, srmRm, srmRmdir A single directory for all file typeA single directory for all file type No directories for each type File assignment to types is virtual File can be placed in SRM-managed directories by maitaining mapping to client’s directory Access control servicesAccess control services Support owner/group/world permission Can only be assigned by owner When file requested by user, SRM should check permission with source site

18. Computing Sciences Directorate, L B N L 18 SC 2003 Examples of Directory Structures (user defined) D1 D3D2 D4 F2 (P) F4 (P)F5 (D) F1 (D)F3 (V) D1 D3D2 D4 F1 (V)F2 (V)F3 (V)F4 (D)F5 (D)F6 (D)F7 (P)F8 (P) (1) Mixed file types(2) By file type Supported function: ChangeFileType Advantage of (1): no need to move files when file types are changed

19. Computing Sciences Directorate, L B N L 19 SC 2003 Concepts: Space Reservations NegotiationNegotiation Client asks for space: C-guaranteed, MaxDesired SRM return: S-guaranteed <= C-guaranteed, best effort <= MaxDesired Type of spaceType of space Can be specified Subject to limits per client (SRM or VO policies) Default: volatile LifetimeLifetime Negotiated: C-lifetime requested SRM return: S-lifetime <= C-lifetime Reference handleReference handle SRM returns space reference handle User can provide: srmSpaceTokenDescription to recover handles

20. Computing Sciences Directorate, L B N L 20 SC 2003 Concepts: Transfer Protocol Negotiation NegotiationNegotiation Client provides an ordered list SRM return: highest possible protocol it supports ExampleExample Protocols list: bbftp, gridftp, ftp SRM returns: gridftp AdvantagesAdvantages Easy to introduce new protocols User controls which protocol to use Default – SRM policy choice How it is returned?How it is returned? The protocol of the Transfer URL (TURL) Example: bbftp://dm.slac.edu/temp/run11/File678.txt

21. Computing Sciences Directorate, L B N L 21 SC 2003 Concepts: Multi-file requests Can srmRequestToGet multiple filesCan srmRequestToGet multiple files Required: Files URLs Optional: space file type, space handle, Protocol list Optional: total retry time Provide: Site URL (SURL)Provide: Site URL (SURL) URL known externally – e.g. in Rep Catalogs e.g. srm://sleepy.lbl.gov:4000/tmp/foo-123 Get back: transfer URL (TURL)Get back: transfer URL (TURL) Path can be different that in SURL – SRM internal mapping Protocol chosen by SRM e.g. gridftp://dm.lbl.gov:4000/home /level1/foo-123 Managing request queueManaging request queue Allocate space according to policy, system load, etc. Bring in as many files as possible Provide information on each file brought in or pinned Bring additional files as soon as files are released Support file streaming

22. Computing Sciences Directorate, L B N L 22 SC 2003 SRM functionality Space reservationSpace reservation Negotiate and assign space to users Manage “lifetime” of spaces Release and compact space File managementFile management Assign space for putting files into SRM Pin files in storage when requested till they are released Manage “lifetime” of files Manage action when pins expire (depends on file types) Get files from remote locations when necessaryGet files from remote locations when necessary Purpose: to simplify client’s task srmCopy: in “pull” and “push” modes

23. Computing Sciences Directorate, L B N L 23 SC 2003 SRM functionality (Cont’d) Space management policies and file sharingSpace management policies and file sharing Policies on what should reside on a storage resource at any one time Policies on what to evict when space is needed Share files to avoid getting them from remote locations Manage multi-file requestsManage multi-file requests Queues file requests, pre-stage when possible Status functionsStatus functions Files: lifetime remaining, what’s available locally Requests: what files are available (needed in lieu of callbacks) Request summary: for progress report Space metadata: space in use, space available, lifetime Provide grid access to/from mass storage systemsProvide grid access to/from mass storage systems HPSS (LBNL, ORNL, BNL), Enstore (Fermi), JasMINE (Jlab), Castor (CERN), MSS (NCAR), SE (RAL) …

24. Computing Sciences Directorate, L B N L 24 SC 2003 SRM Methods File Movement srm(Prepare)Get: srm(Prepare)Put: srmReplicate: Lifetime management srmReleaseFiles: srmPutDone: srmExtendFileLifeTime: Terminate/resume srmAbortRequest: srmAbortFile srmSuspendRequest: srmResumeRequest: Space management srmReserveSpace srmReleaseSpace srmUpdateSpace srmCompactSpace: srmGetCurrentSpace: FileType management srmChangeFileType: Status/metadata srmGetRequestStatus: srmGetFileStatus: srmGetRequestSummary: srmGetRequestID: srmGetFilesMetaData: srmGetSpaceMetaData:

25. Computing Sciences Directorate, L B N L 25 SC 2003 Summary: advantages of using SRMs Synchronization between storage resourcesSynchronization between storage resources Pinning file, releasing files Allocating space dynamically on as “needed basis” Insulate clients from storage and network system failuresInsulate clients from storage and network system failures Transient MSS failure Network failures Interruption of large file transfers Facilitate file sharingFacilitate file sharing Eliminate unnecessary file transfers Support “streaming model”Support “streaming model” Use space allocation policies by SRMs: no reservations needed Use explicit release by client for reuse of space Control number of concurrent file transfersControl number of concurrent file transfers From/to MSS – avoid flooding MSS and thrashing From/to network – avoid flooding and packet loss

26. Computing Sciences Directorate, L B N L 26 SC 2003 Web-Based File Monitoring Tool Shows: -Files already transferred - Files during transfer - Files to be transferred Also shows for each file: -Source URL -Target URL -Transfer rate

27. Computing Sciences Directorate, L B N L 27 SC 2003 File tracking helps to identify bottlenecks Shows that archiving is the bottleneck

28. Computing Sciences Directorate, L B N L 28 SC 2003 File tracking shows recovery from transient failures Total: 45 GBs

29. Computing Sciences Directorate, L B N L 29 SC 2003 File tracking shows network slowdown and recovery Total: 53 GBs

30. Computing Sciences Directorate, L B N L 30 SC 2003 Ongoing and Future Work Ongoing workOngoing work Developing Standard SRM interfaces Particle Physics Data Grid (PPDG) project LBNL, TJNAF, FNAL European Data Grid (EDG) project WP2 - data management WP5 – mass storage Deployment LBNL, BNL, ORNL, TJNAF, FNAL, CERN, (SE-England) Use of SRM by other agents Storage Resource Broker (SDSC) calling HRM to Stage files from HPSS GridFTP invoking HRM New Spec completed (SRM V2.1) directory management File/directory file movement dynamic space management Future workFuture work Access authorization – community access service (CAS) “On-demand” space allocation, accounting, and charging Replica management – invoke SRMs and RLS as a single service Request executer (e.g. DAGMAN) to invoke SRMs SRMs over NeST (Network STorage)