Download Use of Grids in DoD Applications

ANABAS
Use of Grids in DoD
Applications
Geoffrey Fox, Alex Ho
SAB Briefing November 16, 2005
1
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.
2
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)
3
DoD Core Services and WS-* plus GS-* I
NCOW Service or Feature
WS-* Service area
GGF
Others
A: General Principles
Use Service Oriented Architecture
WS-1:
Model
Core
Service
Build Grids
Services
on
Web
Grid of Grids Composition
Industry Best Practice
(IBM, Microsoft …)
Legacy subsystems
modular architecture
and
B: NCOW Core Services (to be continued)
CES 1: Enterprise Services
Management
WS-8 Management
GS-6: Management
CES 2: Information
Assurance(IA)/Security
WS-5
WS-Security
GS-7
(Authorization)
CES 3: Messaging
WS-2, WS-3
Service Internet
Notification
CES 4: Discovery
WS-6 UDDI
CES 5: Mediation
WS-4 Workflow
CES 6: Collaboration
Shared Web Resources
Asynchronous
Organizations
CES 7: User assistance
WS-10 Portlets
GridSphere
CIM
Security
Grid-Shib, Permis Liberty
Alliance etc.
NaradaBrokering,
Streaming/Sensor
Technologies
Extended UDDI
Treatment
of
systems.
Transformations
Virtual
Legacy
Data
XGSP,
Shared
Web
Service ports, Anabas
NCOW
Capability4
Interfaces, JSR168
DoD Core Services and WS-* and GS-* II
NCOW Service or Feature
WS-* Service area
GGF
Others
B: NCOW Core Services Continued
CES 8: Storage (not real-time
streams)
GS-4 Data
NCOW Data Strategy
CES 9: Application
GS-2; invoke GS-3
Best Practice in building
Grid/Web services (proxy
or direct)
Environmental
Services ECS
Control WS-9 Policy
C: Key NCOW Capabilities not directly in CES
System Meta-data
WS-7
Semantic Grid
Globus MDS
C2IEDM,
DDMS, WFS
XBML,
Resource/Service
Matching/Scheduling
Distributed Scheduling Extend
computer
and SLA’s (GS-3)
scheduling to networks
and data flow
Sensors (real-time data)
Work starting
Geographical
Systems GIS
Information
OGC Sensor standards
OGC GIS standards
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
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.
8
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
9
I: Data Mining and GIS Grid
Databases with
NASA, USGS features
SERVOGrid Faults
WFS1
UDDI
Data Mining Grid
WFS3
WFS2
NASA WMS
WMS handling
Client requests
SOAP
WMS
WMS Client
Client
HTTP
10
I: Data Mining Grid
Databases with
NASA,USGS features
SERVOGrid Faults
UDDI
WFS4
SOAP
Pipeline
Filter
PI Data Mining
HPSearch
Workflow
Filter
WS-Context
Narada
Brokering
System Services
WFS3
GIS Grid
11
Hot spots
calculations-areas of
increased
earthquake
probability in
the forecast
time-calculations
are re-plotted
on the map as
features.
12
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 MSRC, DoE, NSF Supercomputers
13
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.
14
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
15
Collaborative Google Maps
with faults from WFS
16
Script III: Collaboration Grid





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
17
Collaboration Grid
WS-Context
HPSearch
UDDI
Narada
Broker
Audio Mixer
Video Mixer
Narada
Broker
WS-Security
Gateway
XGSP Media
Service
Narada
Broker
Gateway
SharedWS
Transcoder
Thumbnail
Replay
Record
Annotate
SharedDisplay
WhiteBoard
18
GIS
TV
Chat
Video Mixer
Webcam
GlobalMMCS SWT Client
19
e-Annotation
e - Annotation
Player
Player
Archived
Archieved
stream list
Stream List
Archived Stream
Archived stream
Player
player
Real time
Real
Time
stream list
Stream List
Annotated
Annotation
/WB
Stream
Player
player
Real time stream
player
e-Annotation
e -Annotation
Whiteboard
Whiteboard
Real Time
Player
20