Difference between revisions of "Operations Procedures"
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
| Operations Centre Management | | Operations Centre Management | ||
| Operations Centres, COD | | Operations Centres, COD | ||
|[[ | |[[PROC02_Operations_Centre_Creation|Operations Centre Creation]] | ||
| Step-by-step instructions on how to create a new Operations Centre | | Step-by-step instructions on how to create a new Operations Centre | ||
|- | |- |
Revision as of 16:54, 17 March 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 |
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. |
EGI Policies and Procedures
See all EGI policies and procedures