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 @

Submitting a middleware requirement

From EGIWiki
(Redirected from Mw-requirements.html)
Jump to navigation Jump to search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Submitting a middleware requirement

NGI/EIRO Operations Centre Managers can submit requirements concerning deployed middleware on behalf of their NGI and their resource centres. Requirements are collected on the requirements hosted on the EGI RT system. These are regularly collected by the Operations Management Board (OMB) on a quarterly basis, but every NGI/EIRO is free to submit a requirement when needed.

Who is responsible of processing middleware requirement tickets? Requirements are discussed and prioritized in the framework of the OMB at least on a quarterly basis, depending on the urgency of the requirement.

Opening a ticket on RT

Go to RT, select the requirements queue (top right-hand corner) from the drop-down menu, and select New ticket.

Setting a middleware requirement ticket

This section provides information on how to properly set the ticket metadata:

  • Owner: "Tiziana Ferrari" from the drop-down menu (this as an indirect way to indicate that the OMB is the owner of the ticket)
  • Category (level 1): "Unified Middleware Distribution" from the drop-down menu
  • Category (level 2): Choose the middleware capability that best matches the requirement, for example Information Discovery for a BDII requirement.
  • Requestor (level 1): "NGI or EIRO" from the drop-down menu
  • Requestor (level 2): select the name of your NGI, or "Other" in case your NGI does not appear in the drop down menu
  • Requestor (level 3): "no value" from the drop-down menu
  • Impact: see priority section of this document.
  • Technology Tag: select the specific middleware distribution if it is applicable to the requirement, or specify "no value" if the requirement is about a generic capability present in different middleware distributions.
  • Custom tag:specify requirement emi if the requirement should be considered for EMI or IGE if relevant to Globus (make sure this is correctly set to ease searches across the Requirements queue)
  • Non Functional Tag: select what is applicable from the drop-down menu, depending on the type of requirement, for example Feature if the requirements is about new functionality not presently available.
  • Describe extensively the feature requested in the body of the ticket and information about use cases if possible.


Priority can be set at the moment of the creation of the ticket. In order to do so, use the Impact field. The priority levels that can be selected in the impact field are in a range of 4 levels, from low to high as follows:

  • Don't know
  • Nice to have - slight improvement
  • Useful – will be of some benefit to this community
  • Important with a measurable benefit to this community
  • Essential to the effectiveness of this community/the wider this community