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.

MAN04 Tool Intervention Management

From EGIWiki
Jump to navigation Jump to search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators


Title Management of central operational tool unscheduled downtimes
Document link https://wiki.egi.eu/wiki/MAN03_Tool_Intervention_Management
Last review Tferrari 13:55, 8 March 2011 (UTC)
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Person E. Imamagic
Document Status draft
Approved Date specify
Procedure Statement This manual provides information on how to manage central operational tool unscheduled downtimes.

Management of central operational tool unscheduled downtimes

The purpose of this document is to describe the intervention in case of unscheduled failure of central operational tool.

Scope

This manual only applies to unscheduled downtimes of central operational tools. List of central operational tool

Scheduled downtimes are management according to existing procedures.

Procedure

In the following sections relevant scenarios are covered.

Case 1: short "undetected" downtime

Description: Service fails and recovers before administrator manages to react (e.g. short power or network outage).

Actions:

  1. Administrator should enter UNSCHEDULED downtime to GOCDB with detailed description of failure (see notification template 4).

Case 2: "detected" downtime

Description: Service fails and administrator detects the problem. The problem takes longer (TODO: longer than 1h?) time to recover.

Actions:

  1. Administrator should announce the failure by using Operations Portal Broadcast tool (see notification template 1).
  2. At the time of recovery administrator should announce the recovery by using Operations Portal Broadcast tool (see notification template 3).
  3. Administrator should enter UNSCHEDULED downtime to GOCDB with detailed description of failure (see notification template 4).

Case 3: prolonged downtime

Description: Service recovery is delayed.

Actions:

  1. Administrator should announce that recovery is taking longer by using Operations Portal Broadcast tool (see notification template 2).

Notification templates

1. Service failure notification

2. Prolonged service failure notification

3. Service recovery notification without detailed information

4. Post mortem analysis

Revision History