MAN02 Service intervention management
|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|
Service intervention management
DISCLAIMER: This manual obsoletes the previous EGEE version maintained on CERN EDMS
|Title||Service intervention management|
|Last modified||19 August 2014|
|Policy Group Acronym||OMB|
|Policy Group Name||Operations Management Board|
|Approved Date||EGEE approved (Oct 2009)|
|Procedure Statement||This manual provides information on how to manage service interventions.|
|Owner||Owner of procedure|
A service intervention is defined as an action which will involve or lead to the possibility of a loss, or noticeable degradation of a service. Depending on the planning of the outage, we have two types of intervention:
- Scheduled interventions: planned and agreed in advance
- Unscheduled interventions: unplanned, usually triggered by an unexpected failure
How to manage an intervention
- Scheduled interventions MUST be declared at least 24 h in advance, specifying reason and duration.
- Existing scheduled interventions CAN be extended, provided that it’s done 24 hours in advance.
- Any intervention declared less than 24 h in advance will be considered unscheduled.
- Sites MUST declare unscheduled interventions as soon as they are detected to inform the users. Unscheduled interventions CAN be declared up to 48 hours in the past (retroactive information to the user community)
The required information to fill in when declaring an intervention are:
- Severity (Outage or Warning)
- Starting and ending dates
- Affected site / Affected services and endpoints
- For interventions that impact end users, the downtime SHOULD be declared 5 working days in advance, specifying reason and duration.
- A post−mortem SHOULD be included in the downtime report.
intervention notifications (through broadcasts, RSS feeds, etc) as specified in the following procedures are automatically sent when declaring a downtime in GOCDB: at declaration time, 24 h in advance and 1 h before the intervention.
Sites on downtime for more than 1 month will be suspended/uncertified. AT_RISK downtime declarations are only for providing warnings to users, and are ignored for calculating site availability (actual status will be used).
|A. Paolini||2016-10-31||Added required information paragraph and a link to downtimes description; changed the contact group to operations.|
|M. Krakowian||2014-08-19||Change contact group -> Operations support|