STORM UNTIL 2013 AND BEYOND Riccardo Zappi INFNCNAF

STORM UNTIL 2013 AND BEYOND Riccardo Zappi INFN-CNAF January 24 -25, 2011 TEG DM & SM, NIKHEF, Amsterdam

Activities 2 Short/Medium term activities: � defined within the EMI context � maintenance and development Other activities are based on requests and suggestions coming from: � Customers (via EGI and EMI, or directly) � Working groups like TEG January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Activities and Improvements (1/3) 3 Robustness: � reactive interventions bug fixes user support � proactive activities: test suites and unit tests standard adoption e. g. File System Hierarchy Standard (FHS) compliance improving product quality January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Activities and Improvements (2/3) 4 High Availability, Fault Tolerance � Twin-BE Service Monitoring � Heartbeat enhancement � Ganglia module Responsiveness � Synchronous Pt. G � Performance on SRM call executions January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Activities and Improvements (3/3) 5 Security � Argus Ban Integration: list on DN and VOMS group � Storage Area protection: Evaluating to use Argus Space Accounting � St. AR (Storage Accounting Record) implementation Catalogue synchronization mechanism � As defined in EMI January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Storage Systems support 6 Sto. RM relies on underlying file systems � It works with any POSIX FS with ACL and EA enabled Sto. RM product is committed to : � support all the wished data access/transfer protocol http(s), � support (s)ftp, gsiftp, dav, xrd, torrent, . . . all the most used, promising and required FS HDFS, NFSv 4. 1 investigate on how to integrate cloud storage solution � 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam January

7 Issues and Solutions to support new SS No ACL support (e. g. AWS-S 3, HDFS) � No more Direct Access support (security issue) � Solutions: No file protocol support: use it as a second tier in a hierarchical configuration (like a MSS) Adapt Sto. RM to use only standard permission (minor flexibility) No EA support � No more default store for checksum values � No more Sto. RM-system metadata with files � Solutions: Use of hidden files (like SVN) short term DB January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Supported Protocols 8 File protocol ( file: // ) support: � file protocol is supported by design since Sto. RM was born to take advantage from Cluster-FS (GPFS and Lustre) � "copy-to-WN" paradigm is used, then other data "access" protocol are (or will be) supported (rfio, xrd) http e https support: � already supported both in read and write mode � require a SRM interaction (srm. Pt. G and srm. Pt. P with specified http(s) as desired protocol) gsiftp, rfio and root January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Protocols under evaluation 9 Web. DAV support � work in progress � It will available in 6 -9 months p. NFS support � NFSv 4. 1 doesn't support EA Checksum � Integration on issue tests are expected : d. Cache and/or Blue. Arc (upon availability) GPFS v 3. 5: Active File Management (AFM) � Tests are ongoing at CNAF January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Sto. RM sustainability 10 Sto. RM is currently developed at CNAF � Sto. RM is included into the portfolio of middleware products of IGI: � it is highly integrate in Tier-1 storage solution IGI is the Italian NGI (National Grid Initiative) and is part of the European Grid Infrastructure (EGI) Sto. RM is developed in the context of EMI, ending in May 2013. Main goals are: Improve robustness and quality � Harmonization (e. g. Argus integration) � Standard adoption (e. g. http(s), file: //, ) � The sustainability is guaranteed by the context January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam

Questions 11 ? January 24 -25, 2011, TEG DM & SM, NIKHEF, Amsterdam