ANABAS

1. ANABAS Use of Grids in DoD Applications Geoffrey Fox, Alex HoSAB Briefing November 16, 2005

2. The Ten areas covered by the 60 core WS-* Specifications \ NCOW (and RTI) needs all of these?

3. Activities in Global Grid Forum Working Groups NCOW needs all of these?

4. The Global Information Grid Core Enterprise Services

5. Major Conclusions I • One can map 7.5 out of 9 NCOW and GiG core capabilities into Web Service (WS-*) and Grid (GS-*) architecture and core services • Analysis of Grids in NCOW document inaccurate (confuse Grids and Globus and only consider early activities) • Some “mismatches” on both NCOW and Grid sides • GS-*/WS-* do not have collaboration and miss some messaging • NCOW does not have at core level system metadata and resource/service scheduling and matching • Higher level services of importance include GIS (Geographical Information Systems), Sensors and data-mining

6. Major Conclusions II • Criticisms of Web services in a recent paper by Birman seem to be addressed by Grids or reflect immaturity of initial technology implementations • NCOW does not seem to have any analysis of how to build their systems on WS-*/GS-* technologies in a layered fashion; they do have a layered service architecture so this can be done • They agree with service oriented architecture • They seem to have no process for agreeing to WS-* GS-* or setting other standards for CES • Grid of Grids allows modular architectures and natural treatment of legacy systems

7. DoD Core Services and WS-* plus GS-* I

8. DoD Core Services and WS-* and GS-* II

9. Grid of Grids Service Architecture for Net-Centric Operations and Warfare Problem:Unable to satisfy interoperability, scalability, and security information management requirements for Net-Centric Operations without an advanced grid-based scalable service oriented framework • Challenges: • Combining scalability and interoperability of Grid and Web Services with DoD real time and security requirements • Supporting legacy systems and standards while maximizing value of new commercial service oriented architectures • Objective:Integrate Global Grid Forum (GGF) information management research to provide a Grid of Grids Middleware for Net-Centric Operations consistent with the Global Information Grid (GIG). • Approach: • Analyze Net-Centric Operations and Warfare (NCOW) service specifications and relate core enterprise services in Net-Centric Enterprise • Services (NCES) to core GGF and Web Services (WS-*) standards • Develop the Grid of Grids architecture and information management middleware to address federation of legacy and new DoD enterprise systems with service oriented mediation between component Grids • Develop prototype for NCES capabilities (Collaboration, Messaging, Management, Security/Information Assurance, Discovery, Mediation, User Assistance, Storage, Applications) with advanced Grid and Web Service standards support • Demonstrate for Geographical Information System • Tech transfer Anabas & Ball Aerospace, Global Grid Forum • Technologies: • Business Process Execution Language • Global Multimedia Collaboration System • Narada Brokering • Web Service Standards • Open Grid Computing Environment • Results: • Phase I middleware addresses 6 of 9 NCOW Core Enterprise Services • Demonstrated GIS application in collaboration grid • Middleware demonstrated with 500 users and 20,000 messages/second • Impact: • A scalable managed interoperable secure architecture and middleware for NCOW • Rapid implementation strategy leveraging commercially pervasive technology • Brought GIG and GGF communities together Team: Indiana University/Anabas (Dr. Geoffrey Fox), Ball Aerospace, AFRL/IFSD (Michelle Cheatham)

10. General Message I • Our proof of concept demonstrates many of the NCOW core enterprise services (CES) implemented using Grid services built on top of the WS-* Web service industry specifications. • We will illustrate the use of the Grid of Grids architecture to integrate heterogeneous systems. The papers describe how all CES can be implemented using Grid technology and this is proposed in phase II SBIR. • Note the adherence to standards with a common line protocol SOAP implies that all service implementations are interoperable and one takes services from multiple sources. Anabas/Indiana University only has to implement some of the key Grid services.

11. General Message II: Why Grids • Web services gives us interoperability but Grids are essential as we aim at Information Management • Grids are the key idea to manage complexity but applying uniform policies and building managed systems • Grids of Grids allows one to build out the management in a modular fashion • Uniform Grid messaging handles complex networks with managed QoS such as real-time constraints • Managed Services and Messaging gives scalability and performance (later slide)

12. Scenario • Laptop 8 Windows Client (small Sony) • Laptop 2 Old Windows Client and PPT machine • Laptop 3 Windows Server • Laptop 4 Linux • Assume no Internet access • List of CES and GS-* WS-* mapping on Laptop 2 followed by complete stream of PPT screen shots if failure • On mapping slide highlight services

13. Script I: Data Mining and GIS Grid • This will show a set of Open Geospatial Consortium (OGC) compatible services implementing a GIS (Geographical Information System) grid supporting streaming of feature and map data. • Intrinsic features of a region are supplemented here by features coming from a data-mining code that is filtering data to predict likely earthquake positions. • This uses discovery, metadata, database, workflow, messaging, data transformation, simulation (data-mining) services. • Note the OGC compatible WFS (Web Feature Service) plays role as a domain specific service interface to a database • This used by Los Alamos for DHS simulations replacing data mining by critical infrastructure simulations

14. Script I: Google Map Grid Service • This first demo also illustrates how the Google map system can be wrapped as a Grid itself front-ended by a OGC Web Map Service. • This is used in a Grid of Grids fashion with Google linked with traditional (NASA) Web Map services. • Illustrates how linking NCOW to commodity Grid technology allows access to major IT resources • Google’s 100,000 computers • DoD DoE NSF Supercomputers

15. Script II: Collaborative Grid Service • This demonstrates how streams can be formed from messages and managed in a uniform way whether maps or video. Collaboration is achieved by multicasting of the input or output streams to Grid services. • Our messaging infrastructure handles all multicasting (using software) transparently to services • First we demonstrate collaborative maps using “shared input ports” on web service

16. Script III: Collaboration Grid • Collaborative Audio-video conferencing on Laptop 3 and 8 with services running on 3 • Collaboration uses basic Grid services – metadata, discovery, workflow, security plus the XGSP stream management services. • Complex collaboration scenarios correspond to additional services for particular shared applications and to gateways in Grid of Grids fashion to H323, SIP and other protocols. Annotation, record, replay, whiteboards, codec conversion, audio and video mixing become services. • We demonstrate MPEG4 transcoding and video mixing services • Only Grid Web service based collaboration environment • Use of Grids ensures scalability and performance (next slide)

17. Performance • Reduction of message delay jitter to a millisecond. • Dynamic meta-data access latency reduced from seconds to milliseconds using web service context service. • The messaging is distributed with each low end Linux node capable of supporting 500 users at a total bandwidth of 140 Mbits/sec with over 20,000 messages per second. • Systematic use of redundant fault tolerance services supports strict user QoS requirements and fault tolerant Grid enterprise bus supports collaboration and information sharing at a cost that scales logarithmically with number of simultaneous users and resources. • Supporting N users at the 0.5 Mbits/sec level each would require roughly (N/500)log(N/500) messaging servers to achieve full capability.

18. ANABAS I: Data Mining and GIS Grid SAB Briefing November 16, 2005

19. I: 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

20. California fault data from Quake Tables fault database via Web Feature Service. Standard Open Geospatial Consortium WMS Clients

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

22. Filter PI Data Mining Filter WS-Context WFS3 GIS Grid Databases with NASA,USGS features SERVOGrid Faults I: Data Mining Grid WFS4 Pipeline SOAP UDDI HPSearchWorkflow NaradaBrokering System Services

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

24. Hot spots calculations--areas of increased earthquake probability in the forecast time-- calculations are re-plotted on the map as features.

25. Electric Power and Natural Gas data from LANL Interdependent Critical Infrastructure Simulations Zoom-in Zoom-out FeatureInfo mode Measure distance mode Clear Distance Drag and Drop mode Refresh to initial map

26. ANABAS I(contd): Google Grid Service SAB Briefing November 16, 2005

27. Google Maps as Service accessed from our WMS Client

28. ANABAS II: Sensor Grid(available on movie) SAB Briefing November 16, 2005

29. Typical use of Grid Messaging in NASA Sensor Grid GIS Grid Grid Eventing Datamining Grid

30. Typical use of Grid Messaging Filter or Datamining Sensor Grid Post afterProcessing Post beforeProcessing Web Feature Service NaradaBrokering Notify WFS (GIS data) Grid Database Archives Subscribe HPSearch Manages GIS Grid WS-Context Stores dynamic data GeographicalInformation System

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

32. Integrating Archived Web Feature Services and Google Maps Google maps can be integrated with Web Feature Service Archives to filter and browse seismic records.

33. ANABAS III: Collaborative Google Grid Service SAB Briefing November 16, 2005

34. Collaborative Google Mapswith faults from WFS

35. ANABAS IV: Collaboration Grid SAB Briefing November 16, 2005

36. Session Server XGSP-based Control Media Servers Filters NaradaBrokering All Messaging Admire SIP H323 Access Grid Native XGSP GlobalMMCS Web Service Architecture Use Multiple Media servers to scale to many codecs and many versions of audio/video mixing WebServices High Performance (RTP)and XML/SOAP and .. NB Scales asdistributed Gateways convert to uniform XGSP Messaging NaradaBrokering

37. Average Video Delays for one broker – Performance scales proportional to number of brokers Multiple sessions One session Latency ms 30 frames/sec # Receivers

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

39. GIS TV GlobalMMCS SWT Client Chat Video Mixer Webcam

40. ANABAS V: Annotation Service SAB Briefing November 16, 2005

41. Archived stream Annotation / WB e - Annotation e - Annotation e-Annotation Archived Stream Annotated e-Annotation Player Player Stream Player Whiteboard player player Whiteboard Player Archived Real Time Real TimeStream List Stream List Player Real time Real time stream Archieved stream list player stream list

42. ANABAS Messaging SAB Briefing November 16, 2005

43. NaradaBrokering 2003-2006 • Messaging infrastructure for collaboration, peer-to-peer and Grids Implements JMS and native high-performance protocols (message transit time of 1 to 2 ms per hop) • Order-preserving message transport with QoS and security profiles • Support for different underlying transport such as TCP, UDP, Multicast, RTP • SOAP message supportand WS-Eventing, WS-RM and WS-Reliability. • WS-Notification when specification agreed • Active replay support: Pause and Replay live streams. • Stream Linkage: can link permanently multiple streams – using in annotation of real-time video streams • Replicated storage support for fault tolerance and resiliency to storage failures. • Management: HPSearch Scripting Interface to streams and brokers (uses WS-Management) • Broker Topics and Message Discovery: Locate appropriate • Integration with Axis2 Web Service Container (?) • High Performance Transport supporting SOAP Infoset