1 / 8

iSERVOGrid Architecture Working Group Brisbane Australia June 5 2003

http://www.grid2002.org. iSERVOGrid Architecture Working Group Brisbane Australia June 5 2003. Geoffrey Fox Community Grids Lab Indiana University gcf@indiana.edu. http://academia.web.cern.ch/academia/lectures/grid/. SERVOGrid Grid Requirements.

grene
Télécharger la présentation

iSERVOGrid Architecture Working Group Brisbane Australia June 5 2003

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. http://www.grid2002.org iSERVOGridArchitectureWorking GroupBrisbaneAustraliaJune 5 2003 Geoffrey Fox Community Grids Lab Indiana University gcf@indiana.edu http://academia.web.cern.ch/academia/lectures/grid/

  2. 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

  3. 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

  4. SERVOGrid Caricature RepositoriesFederated Databases Sensor Nets Streaming Data Database Database Analysis and Visualization Loosely Coupled Filters Closely Coupled Compute Nodes

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

  6. 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

  7. 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

  8. Discussion III • Process • email, 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

More Related