# Presentation: 065150

## DAIS-GSM joint session 

***2004 September 22***

## Intellectual Property Statement

- The GGF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the GGF Secretariat.
- The GGF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this recommendation. Please address the information to the GGF Executive Director (see contact information at GGF website).

## Content

- GSM viewed by DAIS
- DAIS viewed by GSM
- Identification of commonalities and issues

## DAIS viewed by GSM Peter Kunszt CERN

## Content

- Quick overview of GSM
- Capabilities
- What is out of scope
- Dependencies
- Commonalities
- How to make use of each other?

## GSM Overview

- Defining the Storage Resource Manager interface (SRM)
- SRMs give an interface to manage storage
- Mass storage systems (HPSS, etc)
- Disk pools
- Opportunistic storage
- SRMs manages requests

- Storage

- GridFTP, HTTPS, ...

- SRM

## GSM Concepts

- SURL: Site URL is the identifyer by which files are found by the SRM (the handle)
- TURL: Transport URL is the actual ‘real’ URL to access the file with (can be gsiftp:// https:// or even file:/)
- Permanent space : guarantees are being made.
- Volatile space : no guarantees are being made.
- Durable space : guarantee to keep file until expiration and raise alarm if gone (job output management use case)

## Capabilities

**GSM**
- File storage management
- Get and put files into a service
- Protocol negotiation
- Lifetime management
- Manage requests
- Bulk requests
- Volatile and Permanent and Durable space concepts
- Storage space management
- Namespace management
- Data Transfer to other SRM
- Access Control

**DAIS**
- Database data access
- Insertion of data objects
- Updates
- Querying over data objects
- Make result set available (even to 3rd party locations)
- Bulk operations if underlying resource supports it
- Schema management
- Access Control implicit

## Out of scope

**GSM**
- Access to data – TURL is given as a handle, access through supported protocol but not in the interface
- Data synchronization between storage sites
- File Catalogs

**DAIS**
- Files
- File I/O
- Comment: WS-DAI for file access possible (ADF BoF)

## Dependencies

**GSM**
- Underlying storage system semantics
- Transfer protocols
- GSI: transport

**DAIS**
- Database Management systems (for storage space management)?
- OGSA
- WSRF: late binding
- GSI : transport/message (implicit)
- Transfers to put results in place (implicit)

## Commonalities/Differences

- Dealing with persistency, managing data access (only files for GSM)
- Transferring data to/from clients
- Asynch Request management (to some extent)

## How to make use of each other

- DAIS might use GSM space reservation
- Data management services
- Output data sets
- GSM might use DAIS for metadata
- Physical resource metadata
- Data characteristics
- Data management system characteristics
- Data about the file contents
- Fine-grained api?
- Expose the internal DB through DAIS?
- Service composability
- Make sure this is supported on both interfaces
- Data Management req’s
- Import/export operations