Difference between revisions of "Procedure Infrastructure Incident Management"

The management of incidents affecting the production infrastructure is based on TRAC issue tracking system. Open incidents can be browsed using TRAC report1 . Closed incidents can be browsed using TRAC report 2.

The resolution of infrastructure incidents is based on the following steps:

1. incident submission
2. prioritization and assignment
3. 1st level support
4. 2nd level support (optional)
5. management decision (optional)
6. resolution and recovery
7. incident closure

1) Incident Submission

Incident tickets are created in TRAC. Tickets must be created as follows:

• enter your email address
• fill the Summary text box
• fill the Description text box
• select the appropriate Application from the list available, if none of the options available apply to your incident please select the "Other" option
• select the required Priority (optional)
• add other concerned people in CC (optional)
• select the appropriate VREVirtual Research Environment. (optional)

Note: access to TRAC can be requested by emailing to the project support mailing list.

2) Prioritization and Assignment

The Infrastructure Managers assign the correct priority to the incident:

• High: tickets must be solved maximum in 2 working days or in a Maintenance Release
• Normal: tickets must be solved in one week time or in the next Minor/Major Release
• Low: tickets must be solved in two weeks time or possibly in the the next Minor/Major Release

Tickets must also be assigned to one member of the Support Team. This is done either by Infrastructure Managers or by members of the Support Team. The assigned Support Team member is automatically notified by email. All email notifications are also send to the support team mailing list.

3) 1st Line Support

The assigned member of the Support Team analyses the ticket and resolves the issue. Reassignment of the ticket to other members of the Support Team might occur as a result of ticket analysis and resolution.

If the Support Team is not able to close the incident, the ticket is escalated to the TCom for further analysis (functional escalation).

4) 2nd Line Support

The TCom tries to understand and solve the incident.

If the TCom is not able to close the incident, the ticket is escalated for a final decision to the PEB (hierarchical escalation).

5) Management Decision

The PEB takes a final decision to allow the resolution of the ticket.

6) Resolution and Recovery

The Support Team or the TCom solves the incident and recovers the affected service to its normal status.

Different steps apply to the resolution of incident tickets, depending on the nature of the incident :

• To indicate that a problem which required the intervention on the infrastructure has been fixed, the Support Team or TCom member should assign to the Progress field the 100% value.
• To indicate that a software problem has been fixed and is now waiting for integration and testing, the Support Team or TCom member should assign the milestone "Ready to Release" to the incident ticket and assign to the Progress field the 100% value.

7) Incident Closure

The Support Team closes the ticket according to the ticket priority:

• High Priority: tickets can only be closed when the issue has been solved and fixed in the production ecosystem;
• Normal/Low Priority: tickets can be closed if the issue was either (1) solved and fixed in the production ecosystem, or (2) fully understood and a new TRAC task created.

PLEASE NOTE that in case of an intervention on the production infrastructure needed to fix an incident ( e.g. service/GHNgCube Hosting Node. restart) , the entitled Support Team member should fill the Intervention Time field of the incident ticket with the info on minutes spent in the infrastructure activity.

The submitter may re-open the ticket in case he is not satisfied with the ticket response.

The Support Team maintains a knowledge database with information about the incident descriptions and resolutions. All closed tickets should be completed with a incident resolution report including the following points: Problem Description, Affected Services, and Resolution Details. This information must be provided as a final comment to the incident TRAC ticket.

gCube, Hadoop and Runtime Resources

Tickets related to gCube, Hadoop and Runtime resources are followed according to the procedure defined above.

gLite Resources

Tickets related to the usage of gLite resources are managed according to the procedure defined above. However, the support Team may forward the problem to EGI by creating a new ticket in the EGI GGUS support service. The Support Team is then responsible for monitoring the tickets submitted in GGUS and update the corresponding TRAC tickets.

Tickets related to the installation and upgrade of gLite are submitted by email to the corresponding EGI NGIs. These tickets are them processed by NGIs which either provide an immediate resolution to the problem or forward the problem to the EGI GGUS support service.

Best effort support and open discussion on any gLite issue is possible using the gLite-discuss mailing list.