Messaging Description of Work

Here is information about what the EMI Description of Work contains about messaging.


Messaging is described in the JRA1 section of part B (page 87):

The messaging service is a common component in industrial distributed systems, and solutions based on such services have been used for high-level cross-grid applications for a while. Recently this technology has been adopted within the EGEE infrastructure as an integration framework for service monitoring and other operational tools including accounting, ticketing and operational dashboards. It also has been used for publishing event logs from gLite middleware components. Apache ActiveMQ, a JMS system was used for this work as it was seen as the most mature messaging open-source implementation available at the time of implementation that provided the required support in terms of reliability, stability, scalability and access from clients in multiple languages. ActiveMQ has also been used by NDGF to change the communications mechanism in dCache. Other than that, middleware components converging into EMI have not made much use of messaging services so far. An innovative approach in service monitoring, management, as well as accounting based on a common messaging infrastructure would considerably simplify the management and operation of grid services opening them to the use of commercial tools and their integration in standard software distribution like Red Hat, already using very similar technologies. It can also be useful in grid middleware communications, though a clear separation is needed.

To advance in this area, EMI will work on better integration of messaging as a low-level common component in the grid software stacks. This will be done by using off-the-shelf components like ActiveMQ or Red Hat MRG, but will involve work on security integration, along with support for efficient subscription to messaging via integrated client libraries in the required languages. Standard good practices will be defined so that developers could easily develop and deploy secure messaging applications. Following that, the grid middleware components could be adapted to use messaging as an underlying communication mechanism for exchanging execution information. This would enable higher reliability in the grid middleware as well as simplifying grid middleware components by removing the bulk of complex and costly networking code needed to provide failover and reliability in the face of component and network outages.

There are currently two possible solutions that have been evaluated in the community: Apache ActiveMQ (Progress FUSE) and Apache qPid (Redhat MRG). While more experience has been gained with ActiveMQ, it lacks many features that Redhat have added to qPid, such as management interfaces and web consoles. Any final choice of EMI implementation platform needs further evaluation that will be done at the beginning of the project.


Here are the milestones directly involving messaging:

  • MS38: MJRA1.13 - Agreement on common information exchange methods
  • MS40: MJRA1.15 - Service monitoring and management
Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-10-19 - LionelCons
    • 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-2021 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