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 @ egi.eu.
Difference between revisions of "2019-bidding/message-brokers"
| Line 10: | Line 10: | ||
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. | 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 | Currently the number of services is about 3,000 and the number of resource centres is about 260. | ||
== Coordination== | == Coordination== | ||
Revision as of 11:16, 5 November 2019
| 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.
TO UPDATE
Service name: Message brokers
Technical description
The Messaging Service is a backend service for EGI operational tools that need to use a messaging functionality for message communications purposes (i.e. Argo monitoring, APEL, the Operations Portal, EGI Fedcloud etc.). 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 3,000 and the number of resource centres is about 260.
Coordination
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.
Operations
- Daily running of the system in high availability configuration
- Maintenance of probes to test the functionality of the service
Support
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.
Maintenance
- Bug fixing and proactive maintenance of the software
- Changes in the system must be rolled in production in a controlled way in order to avoid service desruption.
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:
- Minimum availability/reliability: 99%/99%
- Response to incident records in GGUS within support hours: Medium (see Description page)
Effort
Bids planning a effort of 4 Person Months/year would allow these services and activities to be addressed appropriately.