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 "Submitting a middleware requirement"
| Line 25: | Line 25: | ||
== Priority == | == 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). | 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). | ||
Revision as of 22:54, 11 January 2011
Submitting a middleware requirement
NGI/EIRO Operations Centre Managers can submit requirements for EMI 2.0 on behalf of their NGI and their resource centres. Requirements are collected on the requirements hosted on the EGI RT system.
Who is responsible of processing middleware requirement tickets? Requirements are discussed and prioritized in the framwork of the Operations Management Board (OMB) at least on a quarterly basis, depending on the urgency of the requirement.
Who is authorized to open a ticket?
NGI/EIRO Operations Centre Managers that are members of the noc-managers SSO group 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 EMI 2.0 requirement ticket
This section provides information on how to properly set the ticket metadata:
- Owner: "Tiziana Ferrari" from the drop-down menu
- Category (leve 1): "Unified Middleware Distribution" from the drop-down menu
- Category (level 2): Choose the category that best matches the 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
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).