Evaluation of message passing for the EMI data area

At PM 7, EMI data has to provide a list of areas where we think we would need message passing. As it seems now, the areas are :

Catalogue Synchroniziation

The currently envisioned solution to keep the SE namespace information and the catalogue location information synchronized is to exchange messages between those services. This topic covered by the EMI data Catalogue Synchronization activity. An initial proposal has been presented at the WLCG workshop in London.

Storage Accounting.

The Storage Accounting information, provided by the SE's and possibly by gLite-FTS might be collected on the site level, national level, experiment level or national level. A message passing infrastructure would nicely allow to match those constrains.

Monitoring Information.

Monitoring information might need to be collected at a central place. Here message passing would offer such an infrastructure.

gLite-FTS : transfer requests and asynchronous notifications.

(Info provided by Oliver) In FTS we have been contemplating uses for messaging too. Most simply for asynchronous notifications but also for receiving requests, even to the extent where a client publishes a request to the message bus and it is automatically picked up by the most appropriate server. We haven't yet studied the requirements on the infrastructure.

-- PatrickFuhrmann - 27-Sep-2010

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2010-09-27 - PatrickFuhrmann
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback