ANABAS

1. ANABAS Use of Grids in DoD Applications Geoffrey Fox, Alex Ho, Marlon PierceSBIR Briefing August 25, 2005 August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

2. H1 H2 H3 H4 Body Container System Processing Service F1 F2 F3 F4 Container Handlers What do Web Services Prescribe? • The specify interfaces for system services (and generally useful services like database) • They specify an interface language (WSDL) for all services • They develop containers and frameworks to use to host services • They specify a message format (SOAP) for ALL messages that defines both application and system actions precisely • They imply a process be started to define domain specific services • There are multiple competing activities from Microsoft and IBM to Apache, IU and Anabas (for example) developing system and application services • Unlike for RTI and CORBA, services from different vendors should interoperate August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

3. What do Grids Add? • Grids use all of the Web Services • They address management and deployment of large distributed systems of services • They address security and management issues of virtual organizations crossing multiple administrative domains • GGF is developing specific services of relevance including job management, many aspects of data and scheduling • GGF has a good process for developing new higher level specifications • For example GGF15 will address Cross enterprise security, Campus Grids, Enterprise Grids, High Performance messaging, GIS Grids, Portals and continue OGSA work integrating data, compute and management August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

4. 4: Application or Community of InterestSpecific Services such as “Run BLAST” or “Look at Houses for sale” 3: Generally Useful Services and Features Such as “Access a Database” or “Submit a Job” or “ManageCluster” or “Support a Portal” or “Collaborative Visualization” OGSAand otherGGF/W3C/ ……… 2: System Services and Features Handlers like WS-RM, Security, Programming Models like BPELor Registries like UDDI WS-* fromOASIS/W3C/Industry 1: Container and Run Time (Hosting) Environment Apache Axis.NET etc. The Grid and Web Service Institutional Hierarchy August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

5. G: User Interface F: Portal: Aggregation, Profiles E: Manipulating and Linking Services D: Brokering Monitoring and Managing Resources and Services C: Electronic Proxy Services for Resources B: Resources A: Pervasive System Services: Security, Collaboration, Messaging, Metadata The Grid and Web Service Functional Hierarchy August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

6. CPUs Clusters Compute Resource Grids Overlay and Compose Grids of Grids MPPs Methods Services Functional Grids Federated Databases Databases Data Resource Grids Sensor Sensor Nets Composing Functionality and Resourcesin the Grid of Grids August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

7. NCOW Grid Flood CIGrid … … DoD Servicesand Filters Flood Servicesand Filters Electricity CIGrid Portals Collaboration Grid Visualization Grid Sensor Grid GIS Grid Compute Grid Data Access/Storage Registry Metadata Physical Network Security Notification Workflow Messaging Critical Infrastructure (CI) Grids built in composite fashion and linked to an NCOW (GiG) Grid August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

8. Mediation and Transformation Services External facing Interfaces Port Port Port InternalInterfaces InternalInterfaces InternalInterfaces Port Port Port Port Port Port Port Port Port Messaging Subgrid or service Subgrid or service Subgrid or service Mediation and Transformation in a Grid of Grids and Simple Services August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

9. ANABAS DoD Services as Part of Grid of Grids August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

10. The Global Information Grid Core Enterprise Services August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

11. The Ten areas covered by the core WS-* Specifications August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

12. Activities in Global Grid Forum Working Groups August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

13. Core Services in Action I August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

14. Core Services in Action II August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

15. Analysis of Grid Technology for DoD • We developed four significant documents • DoD Grid Opportunities for the GiG and NCOW • Grids for the GiG and Real Time Simulations (Proceedings of Ninth IEEE International Symposium DS-RT 2005 on Distributed Simulation and Real Time Applications' Montreal October 10-12 2005) is subset • Appendix on Grid and Web Services covering all basic Grid and Web services • Grid Technology Overview and Status reviews Grids • Grid Application Areas within DoD is a general study of applications of Grids in DoD • Complete list of References for Reports on Grids for GiG and NCOW contains all references in above reports • Implementing some Grid Application Areas within NCOW 1.1 of DoDis not started but is intended to write up specific applications such as demos August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

16. Major Conclusions I • One can map “broadly” NCOW and GiG core capabilities into Web Service (WS-*) and Grid (GGF) architecture and core services • Analysis of Grids in NCOW document inaccurate (confuse Grids and Globus and only consider early activities) • Important “mismatches” on both NCOW and Grid sides • Grid/WS-* do not have messaging and collaboration • NCOW does not have system metadata and resource/service scheduling and matching • Higher level services of importance include GIS (Geographical Information Systems), Sensors and data-mining • Criticisms of Web services in a recent paper by Birman seem to be addressed by Grids or reflect immaturity of initial technology implementations August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

17. Major Conclusions II • NCOW does not seem to have any analysis of how to build their systems on WS-*/Grid technologies in a layered fashion; they do have a layered service architecture so this can be done • In particular do not clearly endorse critical header/body structure of SOAP messages • Grid of Grids allows modular architectures and natural treatment of legacy systems August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

18. Areas in Birman Paper • Information Architecture and Service Description • Document-Centric Nature • Time-critical Events • Life Cycle Support for Services • Reliable Messages • Security • Scalability August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

19. Grids and HLA/RTI I • HLA through IEEE1516 has specified the interfaces for its key services that are supported by RTI (Run Time Infrastructure) • HLA does not specify each message semantics or core system services • RTI implementations are NOT interoperable although each one should support any HLA federation • RTI implementations become a full distributed system environment as need metadata, reliable messaging etc. with simulation support only a small part • Grids can be used in HLA with • Dynamic assignment of compute resources to support federates • Building web service interfaces to federates (XMSF) • Infrastructure to build a new generation of RTI that will use Web system services and just add simulation support August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

20. Grids and HLA/RTI II • HLA specifies • Declaration management – achieved through use of publish/subscribe Grid Messaging (NaradaBrokering) • Data Distribution management – corresponds to geometry sensitive publish and subscribe model (add to NaradaBrokering) • Time management – corresponds to simulation framework (use best event driven and time stepped models – as infrastructure generic, one can support broad range of simulations including classic parallel computing and agent-based simulations) • Object management - Very specific to HLA and should be built as per IEEE1516 • Ownership management - could use Grid virtualization and use metadata catalog catalogs to handle properties – might be generalizable • Federation management - Could generalize to support of general simulation models (federates and federations are a general concept) August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

21. Demo Technology Areas DTA • NaradaBrokering: Grid Messaging • Anabas Collaborative Applications • GlobalMMCS/XGSP Collaborative Stream Management Framework and A/V Conferencing • Geographical Information Systems (GIS) Web Feature Services (WFS) • GIS Web Map Services (WMS) and Clients • GIS Sensor Enablement Services • Wrapping of non Grid Applications as Grids of grids or Grids of Services • Information and meta-data Services • HPSearch Workflow and Management • Portals and Portlets August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

22. IN1 Data Mining and GIS Grid Data Mining Grid Databases with NASA, USGS features SERVOGrid Faults NASA WMS WFS3 WFS1 WFS2 WMS handling Client requests UDDI SOAP HTTP WMS Client WMS Client August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

23. California fault data from Quake Tables fault database via Web Feature Service. Standard Open Geospatial Consortium WMS Clients August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

24. Get Feature Info allows users to get map information. This can also be used to read feature info off the map when creating input data for applications Standard Open Geospatial Consortium WMS Clients August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

25. Filter PI Data Mining Filter WS-Context WFS3 GIS Grid Databases with NASA,USGS features SERVOGrid Faults IN1 Data Mining Grid WFS4 Pipeline SOAP UDDI HPSearchWorkflow NaradaBrokering System Services August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

26. PI demo combines WFS, WMS, and HPSearch for service orchestration. Tool bar items allows you to adjust maps Users set up problems by adding filtered seismic archives from WFS as map layers. August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

27. Hot spots calculations--areas of increased earthquake probability in the forecast time-- calculations are re-plotted on the map as features. August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

28. Typical use of Grid Messaging in NASA Sensor Grid GIS Grid Grid Eventing August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu Datamining Grid

29. August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

30. Typical use of Grid Messaging Filter or Datamining Sensor Grid Post afterProcessing Post beforeProcessing NaradaBrokering Notify WFS Database Archivess Subscribe WS-Context Stores dynamic data HPSearch Manages August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

31. IN2 Google Map Client Archived Real Time Databases withSERVOGrid Faults Sensor Grid Google Central HTTP WFS2 WFS1 SOAP Helper Services Google Map Client UDDI August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

32. IN2: Real Time GPS and Google Maps Subscribe to live GPS station. Position data from SOPAC is combined with Google map clients. Select and zoom to GPS station location, click icons for more information. August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

33. IN2: Integrating Archived Web Feature Services and Google Maps Google maps can be integrated with Web Feature Service Archives to filter and browse seismic records. August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

34. IN2: Integrating Archived Web Feature Services and Google Maps Google maps can be integrated with Web Feature Service Archives to browse earthquake fault records. Faults are typically stored by segment number, so map interfaces are convenient for both verifying continuity and setting up input files for computing problems. August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

35. IN2: Same Screens with Hybrid Maps August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

36. IN3 Google Maps as a WMS Web service Databases with NASA,USGS features SERVOGrid Faults Google Central Google MapsWMS (Gateway) WFS1 WFS2 ….. WMS handling Client requests UDDI SOAP Other Servicesusing results HTTP WMS Client August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

37. Google Maps as Service accessed from our WMS Client August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

38. Data Mining Grid IN4 Server-side Streaming from a WMS Databases with NASA, USGS features SERVOGrid Faults NASA WMS WFS3 WFS1 WFS2 SOAP WMS handling Client requests UDDI Collaborative StreamingGrid NaradaBrokering XGSP Media Service August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

39. Data Mining Grid IN4 Shared Display Streaming from a WMS Databases with NASA, USGS features SERVOGrid Faults NASA WMS WFS3 WFS1 WFS2 SOAP WMS handling Client requests UDDI GMC = GlobalMMCS Client WMS Client Collaborative StreamingGrid NaradaBrokering XGSP Media Service GMC August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

40. NaradaBrokering Web Service WS1 WS2 WS3 NaradaBrokering Web Service Collaboration Shared Output port with replicated recipients Shared Input Port with replicated services August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

41. NaradaBrokering WS1 WS4 WS2 WS5 WS3 WS6 Pipelined Web Service Collaboration • In a workflow, one can invoke collaborative streams on any flow and this splitting is between output port of one and input of next Web Service in chain WS-A WS-B Shared Output Port Shared Input Port August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

42. Gateway Gateway Gateway Gateway XGSP Media Service WS-Context Collaboration Grid NaradaBroker Audio Mixer HPSearch Video Mixer UDDI NaradaBroker Transcoder Thumbnail WS-Security Replay NaradaBroker Record Annotate SharedWS SharedDisplay WhiteBoard August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

43. Annotation of GIS Maps from WMS converted into H261 Video Stream August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

44. GIS TV New GlobalMMCS Client Chat Video Mixer Webcam August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

45. Collaborative Map Pages Google Central • Shared Input Port Anabas Endpoint Anabas Endpoint Anabas Endpoint XML Sharedlet interfacesimilar to WSDL Input to Googleweb page NaradaBrokering August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

46. Impromptu Google Interface August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

47. Impromptu Google Map on Whiteboard August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

48. Grid Service Client SOAP Clients and Services • Thick clients can be Grid (WSDL) endpoints and act as services • Can break thick client up as MVC with Model becoming a service – Message-based MVC View Portlet Model as Service Portal Grid Service SOAP HTTP August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

49. Collaborative “Legacy” Object Java Distributed Object • Shared Output Port with Anabas Endpoint providing Service wrapping of RMI Object RMI Anabas Endpoint Anabas Endpoint Anabas Endpoint XML Sharedlet interfacesimilar to WSDL Output from Java Object NaradaBrokering August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu

50. Collaborative Annotation of Map Pages Google Central • Shared Input Port with replicated white board Anabas Google Endpoint WB Service Anabas WB Service Anabas WB Service XML Sharedlet interfacesimilar to WSDL White Board changes NaradaBrokering August 25 2005 Briefing gcf@iu.edu alexho@anabas.com mpierce@cs.indiana.edu