1. Grid Information Services: alternate models
Beth Plale
Computer Science Dept.
Indiana University
Collaborator:
Peter Dinda, Northwestern
07 June 2002

2. Types of Resource Information
Grid Entity
Description
Organizations
Accountable bodies and owners of resources
People
Resource admins, resource providers, GIS admins
Physical resources
Compute resources, network interfaces, benchmark results, number of users, load
Services
Job manager, load leveler, other GIS’
Comm resources
Link capacity, switch capacity, error rate, drop rate
Software packages
BLAS, LAPACK, etc.
Event producers
Generators of event streams
Event channels
Propagators of event streams
Event dictionaries
List of commonly used event types
Instruments
Radar systems, telescopes, etc.
Network paths
Available bandwidth and expected latency
Network topologies
Hosts, switches, routers
Wireless devices
Wireless hosts, wavepoints, cells, etc.
Virtual organizations
Groups of collaborators
07 June 2002

3. Criteria for Inclusion in GIS
An object in the repository represents an entity in the grid
A grid entity has representation in the resource repository if:
The grid entity can be described
The grid entity has value to more than one application
The grid entity is persistent (exists beyond single application run)
07 June 2002

4. Services Provided by GIS
Query interface: client requests information via query in query language
e.g., SELECT … FROM … WHERE in SQL
Update interface: requests to add information to repository through language interface
e.g., UPDATE … in SQL
07 June 2002

5. Services Provided by GIS
Security interface
Object level or column level?
Access control
Replication interface
Provides replica transparency
Management interface
Turns self on and off
Distribution (not a service, but a necessity)
Hierarchical data partitions easily amongst administrative domains.
07 June 2002

6. Our absolute truths and logical conclusion
Grid entities have complex relationships that are not captured in current GIS’.
The kinds of questions asked of GIS data are more complex than the questions asked today.
Some entities require rapid update rates.
Fast query and update response time, and minimizing size of result are important goals. (1)
Therefore: we are compelled to evaluate multiple data models against performance criteria (1) using use-case query benchmarks.
07 June 2002

7. start Entity Relationship schema diagram relat- ional (mySQL) ldap
represented as
transformed
into
relat-
ional
(mySQL)
ldap
(MDS)
Grid GIS
query
benchmark
XML
(Xindice)
07 June 2002

8. Grid Resources: E-R Diagram
availability
clusters
provides
services
network
cards
name, IP, os,
physicalmemory,
processor.load,
storage.used,
system.uptime
is-a
type,
mfgBW
host,
port,
protocol
made of
batch
queue
hosts
end
points
has
scalapac,
lapack
host
benchmarks
supports
receives/
supplies
instan.
from
application
sources
applications
status
switches
switch
benchmarks
connections
network
paths
routers
traceroute
packet loss,
latency.roundtripDelay.ping,
bandwidth.avail.TCP.singleStream
network
links
network link
benchmarks
07 June 2002

9. Grid Resources: Relational
availability
clusters
services
batch queue
network
cards
type,
mfgBW
name, IP, os,
physicalmemory,
processor.load,
storage.used, system.uptime
host,
port,
protocol
hosts
end
points
host
benchmarks
scalapac,
lapack
application
sources
applications
status
switches
switch
benchmarks
connections
network
paths
routers
traceroute
packet loss,
latency.roundtripDelay.ping,
bandwidth.avail.TCP.singleStream
network
links
network link
benchmarks
07 June 2002

10. Grid Resources: Hierarchical GIS_top network paths connections hosts
clusters
services
end
points
module execs
host
benchmarks
network
cards
module
sources
batch queue
routers
switches
network
links
Relationships
parent, child
(one -> many)
switch
benchmarks
network link
benchmarks
alias (LDAP) or
pointer (XML)
07 June 2002

11. Local control at Admin Domain Level -- similar to DNS
requestor
transformed XML doc 5.
XSLT 1.
Xpath
query
XML doc
XPath
XML doc 4. 2. 3.
SQL
LDAP
XML db
mySQL
LDAP
Local control at Admin Domain Level
-- similar to DNS
07 June 2002

12. Areas of Overlap common schema start Entity Relationship schema
diagram
schema
represented as
Use cases to fuel benchmark queries
transformed
into
relat-
ional
(mySQL)
ldap
(MDS)
Grid GIS
query
benchmark
XML
(Xindice)
07 June 2002

13. ER diagram: Revised Network Topology
nodes
end
points
network
compute
paths A B C D
type:
switch,
router E F AB AC AD BD CD …
“give me all
paths from A to E” G
07 June 2002