iSERVOGrid Architecture Working Group Brisbane Australia June Geoffrey Fox Community Grids Lab Indiana University

SERVOGrid Grid Requirements Seamless Access to Data repositories and large scale computers Integration of multiple data sources including sensors, databases, file systems with analysis system –Including filtered OGSA-DAI Rich meta-data generation and access with SERVOGrid specific Schema extending industry standards Portals with component model for user interfaces and web control of all capabilities Collaboration to support world-wide work Basic Grid tools: workflow and notification

What should SERVOGrid do ? Make use of Grid technologies and architecture from around the world Coordinate with broad community through Global Grid Forum and OMII Decide on domain specific standards SERVOGridML Agree on particular approach within choices in international suite (use GT3 or not?, use portlets or not?, choose meta-data technology) and define SERVOGrid community practice Develop software system infrastructure and applications specific to solid earth science Worry about network interconnection between earthquake scientists and sensors

Database Closely Coupled Compute Nodes Analysis and Visualization Repositories Federated Databases Sensor Nets Streaming Data Loosely Coupled Filters SERVOGrid Caricature

HPC Simulation Data Filter Data Filter Data Filter Data Filter Data Filter Distributed Filters massage data For simulation Other Grid and Web Services Analysis Control Visualize SERVOGrid (Complexity)Computing Model Grid OGSA-DAI Grid Services This Type of Grid integrates with Parallel computing Multiple HPC facilities but only use one at a time Many simultaneous data sources and sinks Grid Data Assimilation

Discussion I People Compute Nodes –ACcESS SGI Altix –RIST Intel/Myrianet –University of Tokyo –VPAC Alpha/Quadrics –Indiana IBM SP –NASA Ames probably Issues –Data formats/translation service for input and output data –Need list of software, databases –Security –Visualization

Discussion II Grid Software Components Core Infrastructure – Apache Axis Metadata Catalog/Registry e.g. Globus MDS but maybe can be done as now in Gateway (as implement for NASA JPL project) Databases – Xindice MySQL plus OGSA-DAI Workflow – Gateway Job Submission – Gateway Portlets for User Interface – Apache Jetspeed

Discussion III Process – , shared internal web pages, external -- iSERVO –Desktop AV, Conferencing Activities –Identify responsible people –Debug collaboration infrastructure –Tutorial from Marlon on current US Project July 2003 –Analyze test cases for hardware, software, data –Policy on machines/data access -- implications