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 @ egi.eu.

Difference between revisions of "EGI Core activities:2013-bidding Message Broker Network"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{TOC_right}}
{{TOC_right}}
'''Go back to the [[Core_EGI_Activities|activity list]].'''
'''Go back to the [[Core_EGI_Activities|activity list]].'''
* Service name:
* Service name: Message broker network
* Service category: Operations
* Service category: Operations
* Service type: Coordination, operation and maintenance
* Service type: Coordination, operation  


The ... is part of the EGI Core Infrastructure Platform ... which supports the daily operations of EGI.
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 =
= 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 =
= 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.
This service includes the following components.


== Coordination ==
== Coordination ==
This activity is responsible of the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it.
This activity is responsible of  
* 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 ==
Support through the EGI helpdesk about  
Support through the EGI helpdesk about the process of message exchange
 
Support about ... is out of scope and is part of activity ''2nd level support (core platform)''.


'''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 (9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization.
Line 25: Line 28:
* Daily running of the system
* Daily running of the system
* Testing and high availability configuration
* Testing and high availability configuration
 
* A test infrastructure to verify the impact of software upgrades on message producers and consumers
== Maintenance ==
* Maintenance of probes to test the functionality of the service
This activity includes:
* core refactoring, bug fixing, proactive maintenance, improvement of the system
* coordination of software maintenance activities with other technology providers that provide software for the EGI Core Infrastructure or remote systems deployed by integrated and peer infrastructures that interoperate with the central EGI components of the system.
* requirements gathering


= Service level targets =
= Service level targets =
*Minimum availability/reliability: ..%/..%
*Minimum availability/reliability: ..%/..%
*Response to incident records in GGUS within support hours: [[FAQ_GGUS-PT-QoS-Levels#Medium_service| Medium]] (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)
*Response to incident records in GGUS within support hours: [[FAQ_GGUS-PT-QoS-Levels#Medium_service| Medium]] (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)

Revision as of 11:47, 3 July 2013


Go back to the 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 of

  • 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 about the process of message exchange

Support hours: eight hours a day (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 the impact of software upgrades on message producers and consumers
  • Maintenance of probes to test the functionality of the service

Service level targets