Difference between revisions of "Operations Procedures"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
{{Template:Op menubar}} | {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} | ||
{{Template:Doc_menubar}} | |||
{{TOC_right}} | |||
= Operations = | = Operations = | ||
Line 20: | Line 18: | ||
| Operations ticket escation | | Operations ticket escation | ||
| Ticket Management | | Ticket Management | ||
| Resource Centre Administrators, Operations Centres, | | Resource Centre Administrators, Operations Centres, Operations | ||
| 20.11.2012 | | 20.11.2012 | ||
|- | |- | ||
Line 27: | Line 25: | ||
| Step-by-step instructions on how to create a new Operations Centre | | Step-by-step instructions on how to create a new Operations Centre | ||
| Operations Centre Management | | Operations Centre Management | ||
| Operations Centres, | | Operations Centres, Operations | ||
| 15.11.2011 | | 15.11.2011 | ||
|- | |- | ||
Line 34: | Line 32: | ||
| Step-by-step instructions on how to decommission an Operations Centre | | Step-by-step instructions on how to decommission an Operations Centre | ||
| Operations Centre Management | | Operations Centre Management | ||
| Operations Centres, | | Operations Centres, Operations | ||
| 22.10.2010 | | 22.10.2010 | ||
|- | |- | ||
Line 41: | Line 39: | ||
| Instructions RODs and Operations Centres on how to handle justification for poor monthly performance | | Instructions RODs and Operations Centres on how to handle justification for poor monthly performance | ||
| Availability and Monitoring | | Availability and Monitoring | ||
| Resource Centre Administrators, Operations Centres, | | Resource Centre Administrators, Operations Centres, Operations | ||
| 30.10.2012 | | 30.10.2012 | ||
|- | |- | ||
Line 48: | Line 46: | ||
| This procedure is part of the [[PROC02|Operations Centre creation]] procedure. | | This procedure is part of the [[PROC02|Operations Centre creation]] procedure. | ||
| Availability and Monitoring | | Availability and Monitoring | ||
| Operations Centres, | | Operations Centres, Operations | ||
| 19.01.2012 | | 19.01.2012 | ||
|- | |- | ||
Line 55: | Line 53: | ||
| 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. | | 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. | ||
| Availability and Monitoring | | Availability and Monitoring | ||
| Operations Centres, | | Operations Centres, Operations | ||
| 23.11.2010 | | 23.11.2010 | ||
|- | |- | ||
Line 62: | Line 60: | ||
| Addition of new OPS Nagios probes to the SAM release. <!-- Comment --> | | Addition of new OPS Nagios probes to the SAM release. <!-- Comment --> | ||
| Availability and Monitoring <!-- Area --> | | Availability and Monitoring <!-- Area --> | ||
| Resource Centre Administrators, Operations Centres, | | Resource Centre Administrators, Operations Centres, Operations <!-- Relevant to --> | ||
| 16.03.2011 | | 16.03.2011 | ||
|- | |- | ||
Line 69: | Line 67: | ||
| Request of 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. <!-- Comment --> | | Request of 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. <!-- Comment --> | ||
| Availability and Monitoring <!-- Area --> | | Availability and Monitoring <!-- Area --> | ||
| Resource Centre Administrators, Operations Centres, | | Resource Centre Administrators, Operations Centres, Operations <!-- Relevant to --> | ||
| 16.03.2011 | | 16.03.2011 | ||
|- | |- | ||
Line 142: | Line 140: | ||
| <br> | | <br> | ||
|- | |- | ||
| [[PROC19|PROC 19]] | | [[PROC19|PROC 19]] | ||
| [[PROC19|Introducing new cloud stack and grid middleware in EGI Production Infrastructure]] | | [[PROC19|Introducing new cloud stack and grid middleware in EGI Production Infrastructure]] | ||
| A procedure for the steps to introduce new stack (Cloud platform) or middleware (Grid Platform) in EGI Production Infrastructure. | | A procedure for the steps to introduce new stack (Cloud platform) or middleware (Grid Platform) in EGI Production Infrastructure. | ||
| Resource Centre Management | | Resource Centre Management | ||
Line 150: | Line 148: | ||
|} | |} | ||
[[Procedure template|Structure template for new procedures]] | [[Procedure template|Structure template for new procedures]] | ||
= Security = | = Security = | ||
{|border="1" class="wikitable sortable" | |||
{| border="1" class="wikitable sortable" | |||
|- style="background-color:lightgray;" | |- style="background-color:lightgray;" | ||
| '''Number''' | | '''Number''' | ||
| '''Title''' | | '''Title''' | ||
| '''Comment''' | | '''Comment''' | ||
| '''Status''' | | '''Status''' | ||
| '''Area''' | | '''Area''' | ||
| '''Relevant to''' | | '''Relevant to''' | ||
|- | |- | ||
| SEC 01 | | SEC 01 | ||
| [https://documents.egi.eu/document/710 EGI Security Incident Handling] | | [https://documents.egi.eu/document/710 EGI 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. | | 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. | ||
| ''approved'', July 2010 (MS405) | | ''approved'', July 2010 (MS405) | ||
| Security | | Security | ||
| Resource Centres, EGI CSIRT | | Resource Centres, EGI CSIRT | ||
|- | |- | ||
| SEC 02 <!-- number --> | | SEC 02 <!-- number --> | ||
| [https://documents.egi.eu/document/717 EGI Vulnerability issue handling process] <!-- title and wiki link --> | | [https://documents.egi.eu/document/717 EGI Vulnerability issue handling process] <!-- title and wiki link --> | ||
| The process used to report and resolve Grid Software vulnerabilities in the EGI Inspire project. <!-- comment--> | | The process used to report and resolve Grid Software vulnerabilities in the EGI Inspire project. <!-- comment--> | ||
| ''approved'', July 2010 (MS405) <!-- status, date of approval --> | | ''approved'', July 2010 (MS405) <!-- status, date of approval --> | ||
| Security <!-- area --> | | Security <!-- area --> | ||
| Resource Centres, Risk Assessment Team, Technology Providers, SVG <!-- Relevant to --> | | Resource Centres, Risk Assessment Team, Technology Providers, SVG <!-- Relevant to --> | ||
|- | |- | ||
| SEC 03 <!-- number --> | | SEC 03 <!-- number --> | ||
| [https://documents.egi.eu/document/283 Critical Vulnerability Operational Procedure] <!-- title and wiki link --> | | [https://documents.egi.eu/document/283 Critical Vulnerability Operational Procedure] <!-- title and wiki link --> | ||
| 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. <!-- comment--> | | 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. <!-- comment--> | ||
| ''approved'', March 15 2011 <!-- status, date of approval --> | | ''approved'', March 15 2011 <!-- status, date of approval --> | ||
| Security <!-- area --> | | Security <!-- area --> | ||
| Resource Centres, Operations Centres, EGI-CSIRT, SVG <!-- Relevant to --> | | Resource Centres, Operations Centres, EGI-CSIRT, SVG <!-- Relevant to --> | ||
|- | |- | ||
| SEC 04 | | SEC 04 | ||
| [https://documents.egi.eu/document/1018 Compromised Certificates and Central Security Emergency suspension] | | [https://documents.egi.eu/document/1018 Compromised Certificates and Central Security Emergency suspension] | ||
| This procedure describes what should be done in the event of a compromised identity certificate, including long lived certificates and proxies. This applies to robot certificates and service certificates as well as user certificates. Certificates are considered to be compromised if they are exposed outside intended policy, or linked to security incidents or malicious jobs. This procedure also addresses usage of Central Security Emergency suspension. The implications of a CA compromise are also briefly described. | | This procedure describes what should be done in the event of a compromised identity certificate, including long lived certificates and proxies. This applies to robot certificates and service certificates as well as user certificates. Certificates are considered to be compromised if they are exposed outside intended policy, or linked to security incidents or malicious jobs. This procedure also addresses usage of Central Security Emergency suspension. The implications of a CA compromise are also briefly described. | ||
| ''approved'', September 27 2013 <!-- status, date of approval --> | | ''approved'', September 27 2013 <!-- status, date of approval --> | ||
| Security | | Security | ||
| EGI CSIRT | | EGI CSIRT | ||
|} | |} | ||
[[ | [[EGI CSIRT:Policies#EGI_Operational_Security_Procedures|More information]] | ||
= EGI Policies and Procedures = | = EGI Policies and Procedures = | ||
See all [[SPG:Documents| EGI policies and procedures]] | See all [[SPG:Documents|EGI policies and procedures]] | ||
[[Category:Operations_Procedures|*]] |
Revision as of 14:56, 23 October 2014
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 | Title | Comment | Area | Relevant to | Last update |
PROC 01 | EGI Infrastructure Oversight Escalation | Operations ticket escation | Ticket Management | Resource Centre Administrators, Operations Centres, Operations | 20.11.2012 |
PROC 02 | Operations Centre Creation | Step-by-step instructions on how to create a new Operations Centre | Operations Centre Management | Operations Centres, Operations | 15.11.2011 |
PROC 03 | Operations Centre decommissioning | Step-by-step instructions on how to decommission an Operations Centre | Operations Centre Management | Operations Centres, Operations | 22.10.2010 |
PROC 04 | Quality verification of monthly availability and reliability statistics | Instructions RODs and Operations Centres on how to handle justification for poor monthly performance | Availability and Monitoring | Resource Centre Administrators, Operations Centres, Operations | 30.10.2012 |
PROC 05 | Validation of Operations Centre Nagios | This procedure is part of the Operations Centre creation procedure. | Availability and Monitoring | Operations Centres, Operations | 19.01.2012 |
PROC 06 | 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. | Availability and Monitoring | Operations Centres, Operations | 23.11.2010 |
PROC 07 | Adding new probes to SAM | Addition of new OPS Nagios probes to the SAM release. | Availability and Monitoring | Resource Centre Administrators, Operations Centres, Operations | 16.03.2011 |
PROC 08 | Management of the EGI OPS Availability and Reliability Profile | Request of 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. | Availability and Monitoring | Resource Centre Administrators, Operations Centres, Operations | 16.03.2011 |
PROC 09 | Resource Centre Registration and Certification | Registration of a new Resource Centre | Resource Centre Management | Resource Centre Administrator, Operations Centres | 15.10.2012 |
PROC 10 | Recomputation of monitoring results and availability statistics | Notification of problems with the monitoring results gathered by SAM and to request a recomputation of results and the related availability and reliability statistics | Availability and Monitoring | Resource Centre Administrators, Operations Centres | 27.09.2012 |
PROC 11 | Resource Centre Decommissioning | Decommissioning of a Resource Centre before it is turned into CLOSED in GOCDB | Resource Centre Management | Resource Centre Administrator, Operations Centres | 15.03.2012 |
PROC 12 | Production Service Decommissioning | Decommissioning of a EGI production service | Resource Centre Management | Resource Centre Administrator, Operations Centres | 24.09.2012 |
PROC 13 | VO Deregistration | Decommissioning of a Virtual Organization supported by the European Grid Infrastructure | VO Management | VO Managers, Operations Manager | 16.07.2012 |
PROC 14 | VO Registration | Registration of a Virtual Organization to the European Grid Infrastructure | VO Management | VO Managers, Operations Manager | 30.10.2012 |
PROC 15 | Resource Center renaming | A procedure for changing name of a Resource Center. | Resource Centre Management | Resource Centre Administrator, Operations Centres | 30.10.2012 |
PROC 16 | Decommissioning of unsupported software | A procedure for removal of unsupported software from production infrastructure. | Resource Centre Management | Resource Centre Administrator, Operations Centres | 20.11.2012 |
PROC 17 | Decommissioning of service type | A procedure for removal of service type from production infrastructure. | Resource Centre Management | Resource Centre Administrator, Operations Centres | 16.07.2013 |
PROC 18 | Temporary Cloud Resource Centre Registration and Certification | A Temporary procedure for registration of a new Cloud Resource Centre. Also apples to certified Resource Centers which introduce cloud resources for the first time. | Resource Centre Management | Resource Centre Administrator, Operations Centres | |
PROC 19 | Introducing new cloud stack and grid middleware in EGI Production Infrastructure | A procedure for the steps to introduce new stack (Cloud platform) or middleware (Grid Platform) in EGI Production Infrastructure. | Resource Centre Management | Resource Centre Administrator, Operations Centres |
Structure template for new procedures
Security
Number | Title | Comment | Status | Area | Relevant to |
SEC 01 | EGI 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. | approved, July 2010 (MS405) | Security | Resource Centres, EGI CSIRT |
SEC 02 | EGI Vulnerability issue handling process | The process used to report and resolve Grid Software vulnerabilities in the EGI Inspire project. | approved, July 2010 (MS405) | Security | Resource Centres, Risk Assessment Team, Technology Providers, SVG |
SEC 03 | Critical Vulnerability Operational Procedure | 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. | approved, March 15 2011 | Security | Resource Centres, Operations Centres, EGI-CSIRT, SVG |
SEC 04 | Compromised Certificates and Central Security Emergency suspension | This procedure describes what should be done in the event of a compromised identity certificate, including long lived certificates and proxies. This applies to robot certificates and service certificates as well as user certificates. Certificates are considered to be compromised if they are exposed outside intended policy, or linked to security incidents or malicious jobs. This procedure also addresses usage of Central Security Emergency suspension. The implications of a CA compromise are also briefly described. | approved, September 27 2013 | Security | EGI CSIRT |
EGI Policies and Procedures
See all EGI policies and procedures