Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @


From EGIWiki
Revision as of 08:44, 14 October 2016 by Psolagna (talk | contribs) (moved 2015-bidding/Phase 3 CheckIn to 2016-bidding/CheckIn: Corrected the address to be in line with the previous format)
Jump to navigation Jump to search
Main 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.

  • Service name: Message brokers


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.

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 350 .


This activity is responsible for

  • the coordination of the system operations and upgrade activities with those partners that are in charge of operating other systems that depend on it to ensure continuity of the service.
  • requirements gathering.


  • Daily running of the system in high availability configuration
  • A test infrastructure to verify interoperability and the impact of software upgrades on depending systems
  • Maintenance of probes to test the functionality of the service


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.

Service level targets

The deployment of the services must ensure:

  • Minimum availability/reliability: 99%/99%
  • Response to incident records in GGUS within support hours: Medium (see Description page)


Bids planning a effort between 2 and 3 Person Months/year would allow these services and activities to be addressed appropriately.