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.
Message brokers
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
| Tools menu: | • Main page | • Instructions for developers | • AAI Proxy | • Accounting Portal | • Accounting Repository | • AppDB | • ARGO | • GGUS | • GOCDB |
| • Message brokers | • Licenses | • OTAGs | • Operations Portal | • Perun | • EGI Collaboration tools | • LToS | • EGI Workload Manager |
Q1: What is the EGI Operations Message Broker Network?
The production EGI Operations Message Broker Network (PROD MSG) is used in order to facilitate the message exchange between the operational tools of EGI. This broker network consists of 4 geographically separated brokers which are operated by 3 institutes: AUTH, CERN and SRCE.
Q2: How can one find the list of the brokers that are part of the PROD MSG Network?
The list of the brokers that are connected to the PROD MSG Network is always available through the BDII information system. It is strongly advised that all producers and consumers that use the PROD MSG Network use the BDII in order to find the brokers that are part of the PROD MSG Network at any time.
Q3: It seems a bit heavy weight to inquire the BDII every time that a consumer or producer wants to use the PROD MSG Network. Is it possible to cache the information?
Yes it is possible to cache the information, but the cache must refresh its information at least every day
Q4: Who can use the PROD MSG Network?
As stated in the answer to Q1, the PROD MSG Network is used in order to facilitate the message exchange between the operational tools of EGI. If the operators of an operational tool, that is not part of the existing set of approved operational tools for the the PROD MSG Network (a table of approved tools follows), want to use the PROD MSG Network, then they have to apply a request via (GGUS??) In their request they have to provide the following information:
- name: a unique short name to identify the operational tool
- description: a multi-line description of what the operational tool does, including pointers (URLs) for more information
- expected activity (if possible: average and peak numbers):
- number of connections (= new sessions) per second
- number of messages per second (received by the broker)
- amplification factor (= number of messages sent by the broker divided by the number of messages received)
- message sizes
- number of clients connected at the same time
- protocol(s) used as stomp|openwire x plain|ssl
- exhaustive list of all destinations used, with wildcards if needed (e.g. /topic/grid.accounting.apel.{ngi} and /queue/Consumer.{role}.grid.accounting.apel.{ngi})
- whether the operational tool is local (i.e. only using one node, messages should not be propagated) or global (network of broker wise); if local, we need the broker(s) that it is allowed to run on
- credentials: a list of accounts/DNs used or a credential source (i.e. Nagios NGI instances from GOCDB)
- security requirements in terms of ACLs: which accounts are allowed to do what on which destinations
Q5: Is it possible to use the PROD MSG Network by other applications apart from operational tools of EGI?
The PROD MSG Network is a critical component for the operational requirements of the Infrastructure. Taking in mind that its capacity are not infinite, it is not advised that the PROD MSG Network is used for applications and tools outside of the operational tools of EGI. We envision that in the future, that the broker service will be yet another component of the UMD and that it will be possible to install it at the site, national and VO level opening the possibility for the creation of a number of service specific networks. Until then, application developers/operators can request for access to the PROD MSG Network and they will have to provide the same information as it is described in the answer for Q4. Apart from this, we require the contact information of the operator of the application and that the application will run for a limited time in the DEVELOPER MSG Network
Following is a list of operational tools, that are already using the PROD broker network:
| Tool | Description or URL |
|---|---|
| SAM | https://wiki.egi.eu/wiki/SAM |