Web Service Grids for iSERVOe-InfrastructureWeb servicesWhat is a Grid?Community ResourcesLarge and Small GridsM2 InteractionsSlide 8Grids and Earthquake Science(i)SERVO Web (Grid) ServicesIntegration of ServicesSlide 12Key Grid Features of iSERVOSlide 14Geographical Information Service (GIS) Data Formats and ServicesQuakeTables+OGC Web Map Service DemoGrid Information Service Integrating GIS Web and Feature ServicesDifferent Performance Issues for iSERVOTwo ways of Linking ModulesGrid Programming ModelWhat is a Simple Service?Grids of Grids of Simple ServicesComponent Grids?Slide 24iSERVO StrategyFurther iSERVO ChallengesArchitecture of (Web Service) GridsImportance of SOAPWeb ServicesWS-I InteroperabilityWeb Services Grids and WS-I+Slide 32Working up from the BottomNaradaBrokeringNaradaBrokering and IOIVirtualizing CommunicationPerformance MonitoringFast Web Service Communication IFast Web Service Communication IIFast Web Service Communication IIIIU SERVO Grid ContributionsWeb Service Grids for iSERVOInternational Workshop on Geodynamics: Observation, Modeling and Computer SimulationUniversity of Tokyo JapanOctober 14 2004Geoffrey FoxCommunity Grids LabIndiana [email protected]e-Infrastructure builds on the inevitable increasing performance of networks and computers linking them together to support new flexible linkages between computers, data systems and people•Grids and peer-to-peer networks are the technologies that build e-Infrastructure•e-Infrastructure called CyberInfrastructure in USAWe imagine a sea of conventional local or global connections supported by the “ordinary Internet”•Phones, web page accesses, plane trips, hallway conversations•Conventional Internet technology manages billions of broadcast or low (one client to Server) or broadcast linksOn this we superimpose high value multi-way organizations (linkages) supported by Grids with optimized resources and system support and supporting virtual (electronic) enterprises•Low multiplicity fully interactive real-time sessions•Resources such as databases supporting (larger) communitiesWeb services•Web Services build loosely-coupled, distributed applications, (wrapping existing codes and databases) based on the SOA (service oriented architecture) principles. •Web Services interact by exchanging messages in SOAP format •The contracts for the message exchanges that implement those interactions are described via WSDL interfaces.What is a Grid?•You won’t find a clear description of what is Grid and how does differ from a collection of Web Services–I see no essential reason that Grid Services have different requirements than Web Services–Geoffrey Fox, David Walker, e-Science Gap Analysis, June 30 2003. Report UKeS-2003-01, http://www.nesc.ac.uk/technical_papers/UKeS-2003-01/index.html. –Notice “service-building model” is like programming language – very personal!•Grids were once defined as “Internet Scale Distributed Computing” but this isn’t good as Grids depend as much if not more on data as well as simulations•So Grids can be termed “Internet Scale Distributed Services” and represent a way of collecting services together to solve problems where special features and quality of service needed.Community ResourcesGrid Community databases have analogy to Television and the News Web that allow individuals to communicate instantly with each other via Web Pages and Headline News acting as proxies N resources deposit information and N can view – Complexity O(N)Large and Small GridsN resources in a community (N is billions for the world and 1000-10000 for many scientific fields)Communities are arranged hierarchically with real work being done in “groups” of M resources – M could be 10-100 in e-ScienceMetcalfe’s law: value of network grows like square of number of nodes M – we call Grids where this true Metcalfe or M2 GridsNature of Interaction depends on size of M or N•Shared Information O(N) Complexity Grids for largish N•Complexity M2 Metcalfe Grids for smaller M < NGrids must merge with peer-to-peer networks to support both Complexity O(N) and M2 SystemsM2 Interactions•Superimpose M2 “Grids” on the sea (heatbath) of O(N) “ordinary” interactionsDatabase DatabaseAnalysis and VisualizationPortalRepositoriesFederated DatabasesData FilterServicesField Trip DataStreaming DataSensors?DiscoveryServicesSERVOGridResearchSimulationsResearch EducationCustomizationServicesFrom Researchto EducationEducationGrid ComputerFarmGeoscience Research and Education GridsGISGridSensor GridDatabase GridCompute GridGrids and Earthquake Science•Complexity N ≈ 1000 to 10000 Community resources building–Thousands of Data Servers of raw and curated data–Services filtering and mining data–Simulation Services–Visualization Services–Geographical Information Services –Registry and metadata Services•These services can support several communities–National and International earth science researchers–Emergency response and critical infrastructure planning and management•Web Services will harmonize different countries (SERVO to iSERVO)•Web Services will harmonize members of a community and between communities with common resources–Curation will bring data to interoperable certified form•National and International research collaborations analyzing particular ideas with many M2 Complexity Grids–Typically many closely knit groups of say around M=10-100 people and services(i)SERVO Web (Grid) Services•Programs: All applications wrapped as Services using proxy strategy•Job Submission: supports remote batch and shell invocations–Used to execute simulation codes (VC suite, GeoFEST, etc.), mesh generation (Akira/Apollo) and visualization packages (RIVA, GMT).•File management:–Uploading, downloading, backend crossloading (i.e. move files between remote servers) –Remote copies, renames, etc.•Job monitoring•Workflow: Apache Ant-based remote service orchestration (NCSA)–Move towards a BPEL framework (can still implement with ANT)•Database services: support SQL queries –Expect Simpler version of OGSA-DAI (“Web Service-DAI”) Grid Database•Data services: support interactions with XML-based fault and surface observation data.–For simulation generated faults (i.e. from Simplex)–XML data model being adopted for common formats with translation services to “legacy” formats.–Migrating to