1. Real Time, Web 2.0, and Grid Systems INGRID 2007 - Instrumenting the Grid 2nd International Workshop on Distributed Cooperative Laboratories - S.Margherita Ligure Portofino, ITALY, April 18 2007 Geoffrey Fox Computer Science, Informatics, Physics Pervasive Technology Laboratories Indiana University Bloomington IN 47401 [email_address] http:// www.infomall.org
2.
3.
4.
5.
6.
7. APIs/Mashups per Protocol Distribution Number of Mashups Number of APIs REST SOAP XML-RPC REST, XML-RPC REST, XML-RPC, SOAP REST, SOAP JS Other google maps netvibes live.com virtual earth google search amazon S3 amazon ECS flickr ebay youtube 411sync del.icio.us yahoo! search yahoo! geocoding technorati yahoo! images trynt yahoo! local
8.
9.
10.
11.
12.
13. Using the Grid of Grids and Core Services to build multiple application grids re-using common components. Physical Network (monitored by FS16) 7: Discovery 8:Metadata BioInformatics Grid Chemical Informatics Grid … Domain Specific Grids/Services … 4: Notification 6: Security 5: Workflow 3: Messaging 9: Management 14: Information Instrument/Sensor 12: Computing Core Low Level Grid Services 9: Management 18: Scheduling 10: Policy 15: Application Services Screening Tools Quantum Calculations 15: Application Services Sequencing Tools Biocomplexity Simulations 11: Portals 17: Collaboration Services 13: Data Access/Storage
14. Net Centric and Critical Infrastructure (CI) Grids built as Grids of Grids and re-using subGrids Flood Services and Filters Physical Network Registry Metadata Military Services and Filters Net Centric Grid Flood CIGrid … Electricity CIGrid … Data Access/Storage Security Workflow Notification Messaging Portals Information Management Grid Collaboration Grid Sensor Grid Compute Grid GIS Grid Core Grid Services
15. Mediation and Transformation in a Grid of Grids and Simple Services Port Port Port Port Internal Interfaces Subgrid or service Port Port Port Port Internal Interfaces Subgrid or service Port Port Port Port Internal Interfaces Subgrid or service Messaging Mediation and Transformation Services External facing Interfaces
16.
17.
18. Dynamic Service Management Architecture Connect to Messaging Node for sending and receiving messages User writes system configuration to registry Manager processes periodically checks available resources to manage. Also Read/Write resource specific external state from/to registry Periodically Spawn WS Management Available in latest release of http://www.naradabrokering.org Always ensure up and running Always ensure up and running
19.
20.
21.
22.
23.
24.
25.
26.
27. These measurements are messages from client to broker and back using latest Java 1.6 release that is about twice performance of earlier releases
30. Average Video Delays (OLD Data) UDP Performance when NaradaBrokering used for audio-video conferencing Latency ms # Receivers One session Multiple sessions 30 frames/sec
31. GlobalMMCS Service Architecture Gateways convert to uniform XGSP Messaging High Performance (RTP) and XML/SOAP and .. Use Multiple Media servers to scale to many codecs and many versions of audio/video mixing NB Scales as distributed Web Services NaradaBrokering Key idea: Use of queues in NaradaBrokering to build multipoint MCU This works well and Naradabrokering is reliable for day long continuous runs Motivated UDP (as well as TCP) support in NaradaBrokering GlobalMMCS is not very reliable software SIP H323 Access Grid Native XGSP Admire Media Servers Filters Session Server XGSP-based Control NaradaBrokering All Messaging
32.
33. Screen capturing Region finding Video encoding SD screen data encoding Network transmission ( RTP ) Network transmission ( TCP ) Video Decoding (H.261) SD screen data decoding Rendering Rendering Screen display HSD Flow Presenter Participants Through UDP NaradaBrokering VSD CSD Through TCP NaradaBrokering
41. Cost of Storage 0 1 2 3 repositories Topology C Topology D Topology E Topology F
42.
43.
44.
45.
46.
47.
48.
49.
50.
51. Indiana Map Grid (Mashup) GIS Grid of “Indiana Map” and ~10 Indiana counties with accessible Map (Feature) Servers from different vendors. Grids federate different data repositories (cf Astronomy VO federating different observatory collections)
52. Browser + Google Map API Cass County Map Server (OGC Web Map Server) Hamilton County Map Server (AutoDesk) Marion County Map Server (ESRI ArcIMS) Browser client fetches image tiles for the bounding box using Google Map API. Tile Server requests map tiles at all zoom levels with all layers. These are converted to uniform projection, indexed, and stored. Overlapping images are combined. Must provide adapters for each Map Server type . The cache server fulfills Google map calls with cached tiles at the requested bounding box that fill the bounding box. Google Maps Server Tile Server Cache Server Adapter Adapter Adapter
53. Mash Planet Web 2.0 Architecture http://www.imagine-it.org/mashplanet Display too large to be a Gadget
60. So there is more or less no architecture difference between Narrow Grids and Web 2.0 and we can build e-infrastructure or Cyberinfrastructure with either architecture (or mix and match) We should bring Web 2.0 People capabilities to Grids (eScience, Enterprises) We should use most convenient services for a given problem See Enterprise 2.0 discussion at http://blogs.zdnet.com/Hinchcliffe / Mashups are workflow (and vice versa) Portals are start pages and portlets could be gadgets