Difference between revisions of "GGUS:Ticket monitoring"

From EGIWiki
Jump to navigation Jump to search
Line 10: Line 10:


== Middleware Tickets ==
== Middleware Tickets ==
Monitoring middleware tickets was discussed several times. The latest agreement is documented in the minutes of the [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1259 GGUS-AB] meeting November 2012.
Monitoring middleware tickets was discussed several times. The latest agreement is documented in the minutes of the [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1259 GGUS-AB] meeting November 2012.<br|
Relevant information is also available here:
Relevant information is also available here:
* [[EGI_DMSU_Ticket_Followup]]
* [[EGI_DMSU_Ticket_Followup]]
Line 16: Line 16:
* [http://www.eu-emi.eu/releases EMI Release Pages]  
* [http://www.eu-emi.eu/releases EMI Release Pages]  
* [[Middleware#Technology_Providers]]
* [[Middleware#Technology_Providers]]
* The assignment of ETA is checked by DMSU.  This process is still valid.
The assignment of ETA is checked by DMSU.  This process is still valid.<br>
* When the ETA date/time arrives, the ticket monitoring checks whether the fix was delivered and is part of any UMD release
When the ETA date/time arrives, the ticket monitoring checks whether the fix was delivered and is part of any UMD release


=== Critical Middleware Tickets ===
=== Critical Middleware Tickets ===

Revision as of 16:01, 7 February 2013

GGUS-logo.jpg


GGUS wiki / GGUS Documentation


GGUS ticket monitoring


This page is in draft version!

Ticket Monitoring Dashboard

For easier triage of critical tickets a dashboard was implemented. This dashboard is linked from the "GGUS tools/reports" section with label "Monitor" on GGUS Home.

Operations Tickets

Operations tickets are submitted via the operations portal. They have ticket type OPS.
Monitoring of OPS tickets is done by the COD team.

Middleware Tickets

Monitoring middleware tickets was discussed several times. The latest agreement is documented in the minutes of the GGUS-AB meeting November 2012.<br| Relevant information is also available here:

The assignment of ETA is checked by DMSU. This process is still valid.
When the ETA date/time arrives, the ticket monitoring checks whether the fix was delivered and is part of any UMD release

Critical Middleware Tickets

  • In case only a few tickets are to be discussed, please add Cristina Aiftimiei in CC field of the tickets (cristina.aiftimiei@pd.infn.it). That will catch her attention and every thing can be kept within the original ticket.
  • In case of many tickets send her the list of tickets by e-mail.
  • If there are doubts about tickets, please submit a ticket to Operations SU referencing the tickets in question. Operations SU will then escalate this to TCB

Other Tickets

The monitoring process for non-operations and non-middleware tickets is documented in File:Other Tickets.pdf in detail. A short summary of required actions is as follows:

  • add comments
  • tag ticket for adding to monitoring dashboard
  • set follow-up date
  • set appropriate remind on date
  • assign ticket to site operations managers if applicable
  • involve NGI operations managers if necessary
  • submit a ticket against "Operations" SU referencing untouched tickets