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.

Submitting a middleware requirement

From EGIWiki
Jump to navigation Jump to search

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 framwork of the OMB at least on a quarterly basis, depending on the urgency of the requirement.

Who is authorized to open a ticket?

OMB members and SA1 task leaders.

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 (leve 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.

<--! * Category (level 3): Choose the category that best matches the requirement, if any. -->

  • Requestor (level 1): "NGI or EIRO" from the drop-down menu
  • Requetor (level 2): select your NGI, or "Other" in case your NGI does not appear in the drop down menu
  • Reqiestor (level 3): "no value" from the drop-down menu
  • Technology Tag: select the specific middleware distribution if it is applicable to the requirement, or specify "no value" if the requirement is about a cross-distribution tool.
  • Custom tag: "requirement emi2"
  • Non Functional Tag: select what is applicable from the drop-down menu, depending on the type of requirement
  • Describe extensively the feature requested in the body of the ticket and indicate -if possible- an example of use case.

Priority

Priority can be set after the creation of the ticket. In order to do so, set the ticket priority by opening the ticket URL, select Basics in the blue bar under the ticket title. The priority levels that can be selected are in the range (specify).