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.

Difference between revisions of "Operations Procedures"

From EGIWiki
Jump to navigation Jump to search
(Undo revision 15490 by Iivanoc (Talk))
Line 113: Line 113:
= EGI Policies and Procedures =
= EGI Policies and Procedures =
See all [[PDT:Policies_and_Procedures|EGI policies and procedures]]
See all [[PDT:Policies_and_Procedures|EGI policies and procedures]]
==> Eddie lives...somewhere in time <==

Revision as of 16:39, 12 April 2011

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


Operations

EGI Operational Procedures are prescriptive documents that describe step-by-step processes involving several partners. The purpose of a procedure is define the related workflow. Procedures are approved by the OMB and are periodically reviewed.

Number Status Area Relevant to Title Comment
PROC 01 approved, October 26 2010 Ticket Management Resource Centre Administrators, Operations Centres, COD COD Escalation Procedure Operations ticket escation
PROC 02 approved, August 17 2010 Operations Centre Management Operations Centres, COD Operations Centre Creation Step-by-step instructions on how to create a new Operations Centre
PROC 03 approved, October 26 2010 Operations Centre Management Operations Centres, COD Operations Centre decommissioning Step-by-step instructions on how to decommission an Operations Centre
PROC 04 approved, August 17 2010 Availability and Monitoring Resource Centre Administrators, Operations Centres, COD Quality verification of monthly availability and reliability statistcs Instructions RODs and Operations Centres on how to handle justification for poor monthly performance through GGUS
PROC 05 approved, August 17 2010 Availability and Monitoring Operations Centres, COD Validation of a Operations Centre Nagios This procedure is part of the Operations Centre creation procedure.
PROC 06 approved, Nov 23 2010 Availability and Monitoring Operations Centres, COD Setting a Nagios test status to OPERATIONS A Nagios probe is set to OPERATIONS when its results are used to generate notifications for the Operations Dashboard. This procedure details the steps to turn a Nagios test to OPERATIONs.
PROC 07 approved, Mar 28 2011 Availability and Monitoring Resource Centre Administrators, Operations Centres, COD Adding new probes to SAM Procedure for adding new OPS Nagios probes to the SAM release.
PROC 08 approved, Mar 28 2011 Availability and Monitoring Resource Centre Administrators, Operations Centres, COD Management of the EGI OPS Availability and Reliability Profile Procedure for requesting a OPS EGI Availability and Reliability profile. A change in the profile is needed every time a new Nagios test needs to be added/removed to/from the profile, in order to have its results included/removed in/from Availability and Reliability monthly statistics.

Note: A Nagios probe is set to AVAILABILITY when its results are used for availability and reliability computation. The procedure to set a Nagios probe to AVAILABILITY will be finalized by TSA1.4 in QR4 2011.

Security

Number Status Area Relevant to Title Comment
SEC 01 approved, July 2010 (MS405) Security Resource Centres, EGI CSIRT Security Incident Handling The "Security Incident Handling Procedure" define site and incident coordinator responsibilities when handling Grid-related security incident. ALL EGI sites are required to follow this procedure to report and handle Grid-related security incident.
SEC 02 approved, July 2010 (MS405) Security Resource Centres, Risk Assessment Team, Technology Providers, SVG Vulnerability issue handling process The process used to report and resolve Grid Software vulnerabilities in the EGI Inspire project.
SEC 03 approved, March 15 2011 Security Resource Centres, Operations Centres, EGI-CSIRT, SVG EGI-CSIRT Critical Vulnerability Handling After a problem has been assessed as critical, and a solution is available, then sites are required to take action. This document primarily defines the procedure from this time, where sites are asked to take action, and what steps are taken if they do not respond or do not take action. If a site fails to take action, this may lead to site suspension.

More information

EGI Policies and Procedures

See all EGI policies and procedures