2016-bidding/message brokers

From EGIWiki
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance


Go back to the EGI Core Activities Bidding page.


The message broker network is a fundamental part of the operations infrastructure ensuring message exchange for monitoring, the operations dashboard and accounting. As such it is a critical core infrastructure platform service component whose continuity and high availability configuration must be ensured.

Given the critical nature of the activity bid must contain an availability and continuity plan for the service.

Technical description

The EGI Production Messaging Infrastructure serves as a backend infrastructure for EGI operational tools that need to use a brokering functionality for message communications purposes (i.e. SAM infrastructure, APEL, the Operations Portal). The service component to be provided needs to provide scalability and redundancy with its topology in order to keep up with the message load produced by the operations tools . The scalability of the service should be adjusted to support the amount of monitoring and accounting data produced by the sites that are part of the EGI Federation of High Throughput Computing, storage and cloud services. Currently the number of services is about 5,000 and the number of resource centres is about 300.


This activity is responsible for



Support of message production, exchange and consumption process through the EGI helpdesk.

Support is provided to the operators of systems that rely on the EGI Message Broker Network capability.

Support hours: eight hours a day (for example 9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization.


Currently the messaging brokers network is based on ActiveMQ brokers, in the EGI-Engage project a new HTTP based messaging solution has being developed. If the transition to the new system will not happen during 2017, the activity will deploy the current system to transition to the new software during 2018.

Service level targets

The deployment of the services must ensure:


Bids planning a effort of 4 Person Months/year would allow these services and activities to be addressed appropriately.

Personal tools