PROC21 Resource Center suspension

From EGIWiki
Revision as of 12:25, 14 May 2015 by Szymocha (talk | contribs) (Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} {{Ops_procedures |Doc_title = Site suspension |Doc_link = |Version = 0...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Main 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 Site suspension
Document link
Last modified 0.1 - 14 May 2015
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group
Document Status Draft
Approved Date
Procedure Statement The document describes the process of site suspension in EGI infrastructure
Owner Owner of procedure


The document describes the process of site suspension in EGI infrastructure. The aim of this procedure is to ensure that the all parties are notified about suspension and that record history is kept.


Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Entities involved in the procedure

  • Site Manager (SiteM): person who is responsible for Site.
  • NGI Representative (NGIR): person who is responsible for NGI Operations.
  • EGI Operations / EGI CSIRT (EGI): person who decides and perform suspension at EGI Level
  • VO Manager (VOM): person resposible for VO. Notified about site suspension.


The reason for suspension should be identified.


Responsible Action Prerequisites, if any
1 NGIR/EGI   Decision about suspension
Site is failing some procedure (could be unresponsive)
2 NGIR/EGI <style type="text/css">p { margin-bottom: 0.25cm; line-height: 120%; }a:link { }</style>

Notification is sent to Site Manager and to NGI Representative – 1 working day on reaction

If there is no reply from Site Manager
  1. Change status of the site in the GOCDB to ‘suspended’.
  1. Register date, site and reason in
  1. Find related VO Managers (VO supported on site according to Dashboard?) accounting/Gstat 
  1. Send a Broadcast to them (at once or monthy?!)

Revision history

Version Authors Date Comments