ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

Catania, Italy, February 10-2-2009

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

A. Santoro, C. Scio*, A. Rocchi, G. Bracco, S. Migliori, A. Quintiliani, S. Podda

ENEA FIM, C.R. ENEA FrascatiV. E. Fermi 45 Frascati ROMA (Italy)

bracco@frascati.enea.itsantoro@frascati.enea.it

(*) Esse3Esse, Roma, Italy

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

ENEA-GRID

• Based on:– AFS (shared filesystem)– LSF Multicluster (resource manager)

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

Many GRIDs...

Grid5000

[W.Gentzsch EGEE'07, Budapest]

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

ENEA-GRID/gLite integrationGateway Approach

From ENEA-GRID to gLite

From gLite to ENEA-GRID

Interface:LSF Multicluster

AFSAFS users

Interface: gLite

PBS/LSF

ENEA-GRID

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

From ENEA-GRID to Glite

Gateway

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

From gLite to ENEA-GRIDShared Proxy Approach for GRID Objects (SPAGO)

CE

WN/UNIX

gLite

WN/UNIX

Proxy

gLite

Shared Filesystem(AFS, NFS, GPFS, ...)

I/OFiles

Resource manager

(LSF or PBS)

• Worker nodes do not mount gLite• CE + Proxy = Gateway

Prompt invocation(LSF, PBS or scripted SSH)

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

Redirection to ProxyWN through wrappersgLite Standard

SPAGO

• WN: JOBSCRIPT– Globus-url-copy input-file– JOB– Globus-url-copy output-file

• WN: JOBSCRIPT– Globus-url-copy input-file

lsrun -m proxy Globus-url-copy input-file– JOB– Globus-url-copy output-file

lsrun -m proxy Globus-url-copy output-file

lsrun: prompt jobexecution

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

Connect now any UNIX WN to the GRID with a loose but solid solution.

NO requirements for WN except SSH and NFS!

AIX

IRIX

MacOSCRAY

Altix

Any Linux

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

The challenge

• Grid middleware changes

– gLite moved to 3.1

– AFS support discontinued

Our Work

– Porting of SPAGO to gLite 3.1; CE analysis and porting

– Creation of a separate daemon to manage AFS tokens

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

CRESCO Project

CRESCO (Computational Research Center for Complex Systems) is an ENEA project cofunded by the Italian Ministry for University and Research (MUR). The project is built around the HPC platform, through the creation of a number of scientific thematic laboratories:

• The Computing Science Laboratory, hosting activities on HW and SW design, GRID technology, and HPC platform management.

• the Computational Systems Biology Laboratory, hosting the activities in the Life Science domain, with activities ranging from genomics to systems biology.

• the Complex Networks Systems Laboratory, hosting activities on complex technological infrastructures.

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

HPC CRESCO InfrastructureTwo Sections:

High memory requests – limited parallelism42 IBM x3850-M2 with 4 Xeon processors Quad-Core Tigerton E7330 (2.4GHz/1066MHz/6MB L2), 32 GB RAM (4 nodes with 64 GB RAM).Total: 672 core

High Parallelism.256 blades IBM HS21 each with 2 Xeon processors Quad-Core Clovertown E5345 (2.33GHz/1333MHz/8MB L2), 8 GB RAM (16 blades with 16 GB RAM).Total: 2048 cores.

Sections connected using Infiniband network 4X DDR; they can operate as a single machine. Total: 2720 cores

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

Interoperability PON/GRISU: CRESCO/PI2S2/Cybersar/SCOPE

• Computational resources– 500 Cores E7330, in section 1.– Core mount Redhat 5.1, not compatible with gLite!!!– Interfaced with the other PON projects using SPAGO

AIX

IRIX

MacOSCRAY

Altix Any Linux

ENEA-GRID and gLite Interoperability: robustness of SPAGO approach

Conclusioni

ENEA approach to GRID projects is focused on interoperability of other infrastructures with ENEA-GRID

ENEA developed an original solution (SPAGO) for gateway implementation with several effects:

interoperability with gLite (EGEE, GRISU).

interconnection of outside grids to every platform/OS in ENEA-GRID

The provided gateways are in production and we havebeen able to follow the evolution of gLite software