1. Globus activities within INFN Massimo Sgaravatto INFN Padova for the INFN Globus group globus@infn.it

2. Globus To implement and use a Grid for real applications some basic services (security, information service, resource management, …) must be implemented as first step Globus identified as possible Grid framework providing these services … but it has been developed mainly for “traditional” computing, different from computing in HEP High throughput vs. High performance PC farms vs Supercomputers Distributed data intensive computing Need to assess what can be used for HEP environment  WP1 “Installation and Evaluation of the Globus Toolkit” of the INFN- GRID Project Goal: evaluation of the Globus toolkit Which services can be useful ? What is necessary to integrate/modify ? What is missing ? Duration: 6 months Results of this first evaluation used to plan future activities

3. Globus Project led by Ian Foster and Carl Kesselman Basic research on GRID (resource management, security, QoS,...) Development of Globus Toolkit Core services for GRID tools and applications

4. Globus Architecture Applications Core Services Metacomputing Directory Service GRAM Globus Security Interface Heartbeat Monitor Nexus Gloperf Local Services LSF CondorMPI NQEEasy TCP SolarisIrixAIX UDP High-level Services and Tools DUROCglobusrunMPINimrod/GMPI-IOCC++ GlobusViewTestbed Status GASS

5. Tasks Security To access GRID resources mechanisms for user authentication needed Evaluation of GSI service Information Service To discover the GRID resources (CPU, storage, network, …) mechanisms to “publish” them must be defined Analysis of GIS service to “publish” information using a uniform and standard interface Resource Management Necessary a uniform interface to submit jobs on GRID resources Uniform standard interface to different resource management systems Uniform standard language for task management Assessment of Globus GRAM service for resource allocation and process management

6. Tasks Data Access and Migration High performance and reliable tools needed to “manage” data (data transfers, wide area replica, …) Assessment of Globus tools for data management (GASS, Globusftp, Replica Management tools) Fault Monitoring Faults in a GRID environment must be promptly detected and recovery mechanisms must be implemented Evaluation of HBM service for fault detection Execution Environment Management Code migration (moving the application where the job will actually be executed) as a possible implementation strategy Evaluation of GEM service to support code migration Globus deployment Reduce complexity and manpower for Globus installation and maintenance

7. Globus installed on ~ 35 machines in 10 sites TORINO PADOVA BARI PALERMO FIRENZE PAVIA MILANO GENOVA NAPOLI CAGLIARI TRIESTE ROMA PISA L’AQUILA CATANIA BOLOGNA UDINE TRENTO PERUGIA LNF LNGS SASSARI LECCE LNS LNL SALERNO COSENZA S.Piero FERRARA PARMA CNAF Status ROMA2

8. Security (GSI) Already done: Evaluation of the Globus security architecture We like the “one time login” paradigm, but some improvements needed Globus certificates (for hosts and users) signed by INFN certification authority Some next steps: Definition and implementation of architecture of CAs Up to task force of the European DataGrid project Periodic update of CRL “Management” of grid-mapfile (where the mappings between local users and GRID users are defined) updates I.e.: a certain Globus resource must be available to all members of a specific physics group

9. Information Service (GIS) Already done: INFN MDS server serving Globus 1.1.1 and 1.1.2 installations (single LDAP server) Lot of problems using the “default” American MDS server Definition and implementation of test architecture of GIS for Globus 1.1.3 installations (distributed model) Web interface for browsing Some next steps: Tests on performance and scalability Results used to define and implement the GIS architecture Review the information gathered from the various machines and published in the GIS

10. Dc=bo, Dc=infn, dc=it,o=grid Bologna GIIS INFN ATLAS GIIS GIIS Dc=mi,Dc=infn, dc=it,o=grid Exp=atlas, o=grid Top Level INFN GIIS Dc=infn,dc=it, o=grid Milano GIS Architecture (test phase) GRIS Implemented Implemented using INFNGRID distribution To be implemented

11. Resource Management (GRAM) Already done: Job submission tests using Globus tools with real applications and in real production environments (GRAM as uniform interface to different underlying resource management systems [LSF, Condor, PBS]) Some bugs found and fixed Many many memory leaks !!! … Some bugs can be solved without major re-design and/or re-implementation Two major problems: Scalability Fault tolerance Submission of Condor jobs to Globus resources (Condor-G and GlideIn) Evaluation of RSL as uniform language to specify resources More flexibility is required Resource administrators should be allowed to define new attributes and users should be allowed to use them in resource specification expressions (Condor Class-Ads model) Cooperation” between GRAM and GIS The information on characteristics and status of local resources and on jobs is not enough (as local resources we must consider Farms) The default schema must be integrated with other info provided by the underlying resource management systems or by specific agents

12. Resource Management (GRAM) Some next steps: Tests with GRAM API Identity a set of useful attributes of a Condor pool, LSF cluster, PBS cluster that should be reported to the GIS, and integrate the default schema

13. GRID Globus deployment (see Zhen’s presentation) Goal: Tools to enable local administrators to deploy the GRID software (now Globus 1.1.3 [and related packages: OpenLDAP, …] + GDMP) Reduce complexity and manpower necessary for installation Decrease errors during installations Collect bug fixes Include INFN customizations Certificates (for hosts and users) signed by INFN CA … but user certificates signed by Globus CA are accepted as well Preliminary architecture for GIS Result: INFNGRID installation toolkit Very very very very useful !!!! Not specific to INFN environments Available to DataGrid partners

14. Data Management Already done: Preliminary tests with GASS and gsiftp To do: Tests with GlobusFTP and Replica Catalog Software (Globus Data Grid Alpha Release 2)

15. Other tasks Fault Monitoring (HBM) Evaluation of HBM for fault detection (for “system” and “user” processes) Data collectors (implementing automatic recovery mechanisms) … but the HBM package is not seeing active development Execution Environment Management (GEM) Evaluation of GEM as service for code migration … but the GEM service now provides only limited capabilities (executable staging)

16. Other info http://www.infn.it/globus