Submitting a middleware requirement

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): "Monitoring" from the drop-down menu
• Category (level 3): "no value" 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
• Reqiestor (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
• Custom Tag: "new nagios probe¹/modify nagios probe²/request nagios probe³"

¹In case of a Category 1 requirement

²In case of a Category 2 requirement

³In case of a Category 3 requirement

• 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).

Nagios test requirement categories

Category 1

This category includes requirements for probes developed by NGI to be integrated into SAM.

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?