Difference between revisions of "EGI Core activities:2013-bidding Message Broker Network"
m (moved 2013-bidding/Message Broker Network to EGI Core activities:2013-bidding Message Broker Network) |
|||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{TOC_right}} | {{Template:Op menubar}} {{Core_services_menubar}} {{TOC_right}} | ||
'''Go back to the [[ | |||
'''Go back to the [[EGI_Core_Activities_Bidding|EGI Core Activities Bidding page]].''' | |||
'''Go back to the [[Core EGI Activities|Core EGI activity list]].''' | |||
* Service name: Message broker network | * Service name: Message broker network | ||
* Service category: Operations | * Service category: Operations | ||
Line 16: | Line 22: | ||
== Coordination == | == Coordination == | ||
This activity is responsible | This activity is responsible for | ||
* the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it. | * the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it. | ||
* requirements gathering | * requirements gathering | ||
Line 23: | Line 29: | ||
Support through the EGI helpdesk of the process of message production, exchange and consumption. Support is provided to the operators of systems that rely of the EGI Message Broker Network capability. | Support through the EGI helpdesk of the process of message production, exchange and consumption. Support is provided to the operators of systems that rely of the EGI Message Broker Network capability. | ||
'''Support hours''': eight hours a day (9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization. | '''Support hours''': eight hours a day (for example 9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization. | ||
== Operation == | == Operation == |
Latest revision as of 15:47, 6 June 2016
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.
Go back to the Core EGI activity list.
- Service name: Message broker network
- Service category: Operations
- Service type: Coordination, operation
The Message Broker Network is part of the EGI Core Infrastructure Platform which is needed to support the running of tools used for the daily operations of EGI.
Introduction
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 infrastructure 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 message broking functionality (i.e. SAM infrastructure, APEL, the Operations Portal). It is a critical system and its topology needs to provide redundancy and to scale to support the message load produced by the operations tools.
This service includes the following components.
Coordination
This activity is responsible for
- the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it.
- requirements gathering
Support
Support through the EGI helpdesk of the process of message production, exchange and consumption. Support is provided to the operators of systems that rely of 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.
Operation
- Daily running of the system
- Testing and 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
Service level targets
- Minimum availability/reliability: 99%/99%
- Response to incident records in GGUS within support hours: Medium (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)