130 likes | 149 Views
Extension of the Social Grid Agents Functional Engine. Dr. Gabriele Pierantoni (TCD) Dr. Keith Rochford (DIAS) Dr. Brian Coghlan (TCD) Dr. Eamonn Kenny (TCD). Social Grid Agents. Social Grid Agents were born as a Resource Allocation System for Grid Computing
E N D
Extension of the Social Grid Agents Functional Engine Dr. Gabriele Pierantoni (TCD) Dr. Keith Rochford (DIAS) Dr. Brian Coghlan (TCD) Dr. Eamonn Kenny (TCD)
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)
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
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.
Information Agnosticism External Information Sink Internal Information System External Information Source
The Functional Engine Manager M M Processor Provider
Why Functional ? 1 Manager Key action, ... Provider/Processor Key action (n-1), ... Action (n) Processor
Why Functional ? 2 Key R Key A Object 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)
Extension of the functional engine Information on who does what Manager Processor Provider Information on how (high level) to do what. Information on how (low level) to do what. This is the best place to extend the functional engine
Extension of the funtional keys Existing Fields of the Action key • Description • Status • Input • Output • Policies • Modalities • EnforcedModalities • Requester • Beneficiary • PreActionNotifications • PostActionNotifications • ExceptionNotifications Notification Extenstions
Benefits of the extension Manager AFTER P Manager BEFORE P
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
Scenarios • Job submission • Indexes (White and Yellow Pages) • Markets • Monitoring Systems • ... • ...