TeraGrid Community Software Areas(CSA)

JP (John-Paul) NavarroTeraGrid Grid Infrastructure Group

Software Integration

University of Chicago and Argonne National Laboratory

March 2006

TeraGrid Platform Challenge

•AIX 5.{1,2,3} on Power{3,4,5}•Solaris 9 on UltraSparc IV•Tru64 on Alpha EV{68,7}•SGI ProPack 4 on IA-64•SLES 9 on PPC64 IBM BlueGene•SUSE 9 on Opteron Cray XT3•SLES8 on IA-64•6 distributions on Linux on IA-32

Software Deployment Options

•Site/Resource Selected– Operating System or Distribution (local)– Scheduler and resource manager (network, possibly local)

– Monitoring system (local, possibly network)– Vendor compiler, vendor MPI (network)

•CTSS - Common TeraGrid Software Stack– Administrator installed– Network file-system (TG_APPS_PREFIX)

•Personal Software– User installed– Network file-system (HOME)

•Community Software– Group installed– Network file-system (TG_COMMUNITY)

Requesting a CSA

•Web request form–Community name–Space requirement–Owner & maintainers–Which TeraGrid resources

•Request processing–Request distributed to sites–Tracked in TG ticket system

CSA Usage

Network shared directory–Owner, community specific group–Group write permissions–Group controls world access to software

Universal path- $TG_COMMUNITY/<community_name>/…

Restrictions–No privileged access–No permanent services

Directions

•TeraGrid wide shared CSA–Wide-area GPFS

•More TeraGrid communities–Open Science Grid (OSG)–Gateways

•Software environment support•Useful for multi-grid interoperability–PRAGMA and other Grids can deploy their software on the TeraGrid