140 likes | 257 Views
Experiences with GridWay on CRO NGI infrastructure. Emir Imamagic, Srce EGEE User Forum 2009, Catania, Italy. Overview. Introduction CRO NGI Middleware User Community GridWay Why do we like it? How could we like it even more? Conclusion. Introduction.
E N D
Experiences with GridWay on CRO NGI infrastructure Emir Imamagic, Srce EGEE User Forum 2009, Catania, Italy
Overview • Introduction • CRO NGI • Middleware • User Community • GridWay • Why do we like it? • How could we like it even more? • Conclusion
Introduction • Initial grid national initiative in Croatia – 2003 (CRO-GRID) • Providing a job management interface is crucial for attracting cluster user communities • Started using GridWay in 2005 • The best among very few (working) solutions • Truly middleware-independent • We met developers on EGEE Conference, Geneva, 2006
CRO NGI • Grid infrastructure provided for academic & research purposes • Government approved, permanent grid service • Community • 8 partners • 23 user institutions • 80 users • 42 active users
Middleware • Sites • Standard cluster environment (OSCAR distribution) • Torque, Maui and SGE batch systems • Ganglia monitoring system • Grid • Globus Toolkit 2 (GRAM, GridFTP) • Globus Toolkit 4 (WS-GRAM, WS-MDS, RFT) • Job metascheduling and management • Condor-G with GRAM • GridWay with WS-GRAM
User Community • Traditional cluster users • Applications: • Gaussian (computational chemistry) • Gromacs (molecular dynamics) • ABINIT(computational chemistry) • Povray & FFmpeg (graphic rendering) • Intel Math Kernel Library (mathematics) • NAG Fortran Libraries (mathematics) • Home-grown applications
GridWay • Grid Metascheduler • Transparent job management over heterogeneous resources • Enables integration with various middleware systems (e.g. Globus Toolkit, UNICORE, gLite, NorduGrid, …) • Standards compliant • OGF DRMAA API • OGF JSDL • Aligned with Globus Toolkit
Why do we like it? • Multiple middleware systems support • Convenient for heterogeneous environments • Enables transparent changes of underlying infrastructure • Positive feedback from users • Easy to use – similar to cluster & OS-level tools • Job recovery in case of service/resource failures • Advanced scheduling policies • Fair share – complaint with cluster policy
Why do we like it? • Advanced job options • Checkpointing – automatic storing of checkpoint on remote GridFTP server • Performance tracking & automatic migration to better resources • Modular & extendable • Modifying job wrappers to suite our environment • Possibility to add custom scheduling policy • Open source • Modifying core code is possible
How could we like it even more? • Periodic glitches • User proxy rejected(“could not register user error”) • Problem with staging files (seems gone in 5.4) • MADs performance • Heavyweight MAD processes present even if no job is running (roadmap #4484)
How could we like it even more? • Improved integration with underlying layers • Adding more resource attributes for ranking and filtering(roadmap #4492) • Passing attributes to underlying middleware, e.g. WS-GRAM extensions (roadmap #4491) • Robustness • Too sensitive to network failures • Too sensitive to middleware glitches • Jobs do not recover properly after restart (bug #5308)
Conclusion • GridWay – open grid metascheduling solution • Enables more than best effort grid scheduling • Suitable for heterogeneous grid environments with tendency to change
Thank You!Questions? http://www.cro-ngi.hr