Extension of the Social Grid Agents Functional Engine

1
Extension of the Social Grid Agents Functional
Engine

• Dr. Gabriele Pierantoni (TCD)
• Dr. Keith Rochford (DIAS)
• Dr. Brian Coghlan (TCD)
• Dr. Eamonn Kenny (TCD)

2
Social Grid Agents

• Social Grid Agents were born as a Resource
  Allocation System for Grid Computing
• Ideally, we would like them to become a
  Allocation System for Distributed Computing
• They are based on the concept of agnosticism,
  both from a technological and economic point of
  view.
• It allows the common harnessing of different Grid
  Middlewares (technological agnosticism)
• It allows different allocation models to coexist
  (economic agnosticism)

3
General Architecture
Economic Agnosticism
S.G.A.
S.G.A.
S.G.A.
P.G.A.
P.G.A.
P.G.A.
Technological Agnosticism (Translation Borders)
Resource
Resource
Resource
Different Technologies
4
Agnosticism on what ?

• Although Social Grid Agents can be defined as
  technologically agnostic they nevertheless
  implement a very specific information system.
• This information system is based on
  agent-to-agent messaging.
• This feature weakens their technological
  agnosticism and, therefore, their ability to be
  connected to different information systems.

5
Information Agnosticism
External Information Sink
Internal Information System
External Information Source
6
The Functional Engine
Manager
M
M
Processor
Provider
7
Why Functional ? 1
Manager
Key action, ...
Provider/Processor
Key action (n-1), ...
Action (n)
Processor
8
Why Functional ? 2
Key A
Object
Key R
Key B
Object
Key C
Object

• MatchMaking based on ClassAd (functional
  language) that allows
• Matchmaking (yes or no)
• Ranking (Best of, better then)
• Partial Evaluation (support for the concept of
  UNDEFINED)

9
Extension of the functional engine
Information on who does what
Manager
Processor
Provider
Information on how (low level) to do what.
Information on how (high level) to do what.
This is the best place to extend the functional
engine
10
Extension of the funtional keys

• Description
• Status
• Input
• Output
• Policies
• Modalities
• EnforcedModalities
• Requester
• Beneficiary
• PreActionNotifications
• PostActionNotifications
• ExceptionNotifications

Existing Fields of the Action key
Notification Extenstions
11
Benefits of the extension
Manager
AFTER
P
Manager
BEFORE
P
12
Possible Implementations

• Standards-based using OASIS WS-Notifications

GT4 Container
Apache MUSE
SGA Message
S.G.A.
Producer
WS-Notifications
Apache MUSE
WS-Notifications
Consumer
13
Scenarios

• Job submission
• Indexes (White and Yellow Pages)
• Markets
• Monitoring Systems
• ...
• ...