1. Why do we need PGI? http://www.unicore.eu Shahbaz Memon m.memon@fz-juelich.de Jülich Supercomputing Centre (JSC)

2. 2 http://www.unicore.eu  Open source under BSD license with software hosted on SourceForge  Standards-based: OGSA-conform, WS-RF 1.2 compliant  Open, extensible Service-Oriented Architecture (SOA)  Interoperable with other Grid technologies  Seamless, secure and intuitive following a vertical end-to-end approach  Mature Security: X.509, optional proxy and VO support  Workflow support tightly integrated while being extensible for different workflow languages and engines for domain-specific usage  Application integration mechanisms on the client, services and resource level  Variety of clients: graphical, command-line, API, portal, etc.  Quick and simple installation and configuration  Support for many operating systems (Windows, MacOS, Linux, UNIX) and batch systems (LoadLeveler, Torque, SLURM, LSF, OpenCCS)  Implemented in Java to achieve platform-independence Guiding Principles

3. 3 http://www.unicore.eu Architecture & PGI Adoption Architecture & PGI Adoption emerging standard interfaces Grid services hosting job incarnation & authorization authentication scientific clients and applications parallel scientific jobs of multiple end-users on target systems UNICORE WS-RF hosting env. Service Registry UNICORE WS-RF hosting environment XNJS IDB UNICORE Atomic Services OGSA-* XACML entity UNICORE WS-RF hosting environment XNJS IDB UNICORE Atomic Services OGSA-* XACML entity ByteIO BES RUS HPC-P UR JSDL XACML ByteIO BES RUS HPC-P UR JSDL XACML X.509 SAML CIS GLUE 2.0 command- line client Eclipse- based client Portal client, e.g. GridSphere Programming API Local RMS (e.g. Torque, LL, LSF, etc.) Target System Interface Local RMS (e.g. Torque, LL, LSF, etc.) Target System Interface USpace Storage SRM GridFTP Proxies DRMAA XUUDB UVOS WS-ISOAPJSDLWS-RFX.509Proxies Gateway

4. 4 http://www.unicore.eu  Answers to the question “Why do we need PGI?”…  UNICORE is primarily driven by High Performance Computing (HPC) needs in production infrastructures  e.g. HPC-driven EU DEISA, Russian-Belarus SKIF-Grid, …  Compliance to PGI enables the use of HPC applications in conjunction with rather High Throughput Computing (HTC) – driven infrastructures (i.e. EGEE, NorduGrid, NGS,…)  Avoiding workarounds/hacks to achieve interoperability with HTC-driven middleware on a pair-wise fashion (i.e. gLite/EGEE, ARC/NorduGrid) in order to run HTC/HPC scientific workflows  Enable scientists to use HTC infrastructures/resources for small- scale evaluation jobs before doing full-blown production with up to 16.000 cores and more on large-scale HPC resources  Enable HTC infrastructure users with an easy way to use HPC PGI Perspective