Page tree
Skip to end of metadata
Go to start of metadata

Document control

AreaEGI Federation Operations
Procedure status

FINAL

OwnerAlessandro Paolini 
ApproversOperations Management Board
Approval status

APPROVED

Approved version and date

v5,  

Statement

The document describes the process for suspending a Resource Centre in the EGI infrastructure

Next procedure reviewupon request

Procedure reviews

The following table is updated after every review of this procedure.

DateReview bySummary of resultsFollow-up actions / Comments

 

Alessandro Paolini copy from PROC21_Resource_Center_suspension in EGI Wiki. Updated some links and information.

 

Alessandro Paolini removed the need to notify the VO managers.

Table of contents

Overview

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

Definitions

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

  • Resource Centre Manager: person who is responsible for Resource Centre.
  • NGI Representative (NGI): person who is responsible for NGI Operations.
  • EGI Operations / EGI CSIRT (EGI): person who decides and perform suspension at EGI Level

Triggers

Resource Centre can be suspended either by NGI operators or EGI Operations in case of breaking  Resource Centre Operational Level Agreement

  • PROC01: Resource Centre is failing EGI Infrastructure Oversight escalation procedure
    • Level 3: NGI/ROC operations manager should make Resource Centre responsive or suspend it
    • Level 4: If no action was taken by NGI/ROC operations manager for 5 working days Operations send an mail to NGI/ROC operations manager with CC to site administrator, ROD and GGUS. If no response after 1 working day Operations performs Resource Centre suspension.
  • PROC04: Resource Centre is underperforming (below the OLA target) for 3 consecutive months
  • PROC16: Resource Centre is failing Decommissioning of unsupported software procedure
    • Follow up the migration: Resource Centre which didn't provide information on migration plans can be suspended
  • SEC01-05: Resource Centre is failing Security Incident or Critical Security procedure

Notes for suspended sites

  • suspended sites are not displayed in GGUS
  • when a site gets suspended in GOC DB the "Notified site" field is flushed automatically in the corresponding tickets, and NGIs start managing them (processing or closing is up to them)Steps

Steps

#ResponsibleActionNotes
1NGI/EGIDecision about suspension
2NGI/EGI

Notification is sent to Resource Centre Manager and to NGI Representative – 3 working day on reaction


3NGI/EGIIf there is no reply from Resource Centre Manager
  • Change status of the Resource Centre in the GOCDB to ‘suspended’ adding the reason.
  1. If NGI is realizing procedure: Send notification to Resource Centre Manager.
  2. If EGI is realizing procedure: Send notifications to NGI Representative and Resource Centre Manager.