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 "Submitting a middleware requirement"

From EGIWiki
Jump to navigation Jump to search
(Created page with '= Submitting a Nagios test requirement = NGI/EIRO Operations Centre Managers can submit requirements for '''EMI 2.0''' on behalf of their NGI and their resource centres. Require…')
 
 
(33 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Submitting a Nagios test requirement =  
{{Template:Op menubar}}
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 [https://rt.egi.eu/rt/ RT] system.  
{{TOC_right}}
[[Category:Middleware]]
= 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 [https://rt.egi.eu/rt/ 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 Nagios test tickets? Nagios test requirements are discussed and prioritized in the framwork of the Operations Tool Advisory Group ([https://wiki.egi.eu/wiki/OMB OMB]) at least on a quarterly basis, depending on the urgency of the requirement.
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.
 
== 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 ==
== Opening a ticket on RT ==
Go to [https://rt.egi.eu/rt/ RT], select the ''requirements'' queue (top right-hand corner) from the drop-down menu, and select ''New ticket''.
Go to [https://rt.egi.eu/rt/ RT], select the ''requirements'' queue (top right-hand corner) from the drop-down menu, and select ''New ticket''.


== Setting a Nagios probe requirement ticket ==
== Setting a middleware requirement ticket ==
This section provides information on how to properly set the ticket metadata:
This section provides information on how to properly set the ticket metadata:
* Owner: "Daniele Cesini" from the drop-down menu
* 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 1): "Unified Middleware Distribution" from the drop-down menu
* Category (level 2): "Monitoring" 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): "no value" from the drop-down menu
<!-- * Category (level 3): Choose the category that best matches the requirement, if any. -->
* Requestor (level 1): "NGI or EIRO" from the drop-down menu
* 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  
* Requestor (level 2): select the name of 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
* Requestor (level 3): "no value" from the drop-down menu
* Technology Tag: select the specific middleware distribution if relevant, or specify "no value" if the requirement is applicable to all stacks
* Impact: see '''priority''' section of this document.
* Custom Tag: "new nagios probe<sup>1</sup>/modify nagios probe<sup>2</sup>/request nagios probe<sup>3</sup>"
* 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.
<sup>1</sup>In case of a [https://wiki.egi.eu/wiki/Nagios-requirements.html#Category_1 Category 1] requirement
* 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.


<sup>2</sup>In case of a [https://wiki.egi.eu/wiki/Nagios-requirements.html#Category_2 Category 2] requirement
* Describe extensively the feature requested in the '''body''' of the ticket and information about use cases if possible.  
 
<!--* '''Important: if the requirement is submitted directly from a Site Manager, please in the first line of the message ''body'' specify the ''Site name'' as it appears in the ''GOCDB'' writing: '''"SITE:<sitename>"-->
<sup>3</sup>In case of a [https://wiki.egi.eu/wiki/Nagios-requirements.html#Category_3 Category 3] requirement
 
* Non Functional Tag: select what is applicable from the drop-down menu, depending on the type of requirement


== 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 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''
== Nagios test requirement categories ==
* ''Nice to have - slight improvement''
 
* ''Useful – will be of some benefit to this  community''
=== Category 1===
* ''Important with a measurable benefit to this community''
This category includes requirements for probes '''developed by NGI to be integrated into SAM'''.
* ''Essential to the effectiveness of this community/the wider this community''
 
A ticket can be submitted in this category if the NGI/EIRO wishes to share a probe internally developed that may be potentially applicable and useful to the whole EGI.
 
For each probe in this category, the requesting NGI/EIRO should specify the following information in the body of the ticket:
 
* '''Grid service that probe tests''': specify which feature of the service is tested by the probe (e.g. CPU load)
 
* '''Brief description of test''': provide a high-level description of the test including the conditions that generate a WARNING and CRITICAL result.
 
* '''Developer contact information'''
 
* '''Link to existing documentation (if any)'''
 
=== Category 2===
This category is applicable to tickets that are submitted to request '''changes to existing probes''', in the case an NGI/EIRO needs to require a change to a test already distributed.
 
For each probe in this category, the requesting NGI/EIRO should specify the following information in the body of the ticket:
 
* '''Test name'''
 
* '''Brief description of changes requested''': please provide here information on what should change, and provide information on a use case that justifies this change.
* '''Is NGI prepared to develop changes?'''
 
=== Category 3===
A ticket can be submitted to request that a test is developed. Tests that are relevant are those applicable to the whole NGI. Tests that are requested for regional deployment and just address local requirements are out of scope.
 
For each probe in the body of the ticket provide the following information:
 
* '''Grid service that should be test:''' provide information on
** which metric the probe should return
** other specific probes currently existing for this service.
 
* '''Write a brief description of the probe''', this including a use case.
 
* '''Is NGI prepared to develop probes?'''

Latest revision as of 15:09, 4 December 2012

Main EGI.eu 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

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