Difference between revisions of "Operations Procedures"
Jump to navigation
Jump to search
Line 4: | Line 4: | ||
{{TOC_right}} | {{TOC_right}} | ||
= 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. | 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. | ||
Line 60: | Line 61: | ||
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. | 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 procedures = | |||
{|border="1" class="wikitable sortable" border="1 | |||
|- style="background-color:lightgray;" | |||
| '''Number''' | |||
| '''Status''' | |||
| '''Area''' | |||
| '''Relevant to''' | |||
| '''Title''' | |||
| '''Comment''' | |||
|- | |||
| SEC 01 | |||
| ''approved'', July 2010 (MS405) | |||
| Security | |||
| Resource Centres, EGI CSIRT | |||
| [https://documents.egi.eu/document/47 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, SVG, Technology Providers | |||
| [https://documents.egi.eu/document/47 Vulnerability issue handling process] | |||
| The process used to report and resolve Grid Software vulnerabilities in the EGI Inspire project. | |||
|- | |||
|} | |||
= 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]] |
Revision as of 16:51, 10 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 procedures
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, SVG, Technology Providers | Vulnerability issue handling process | The process used to report and resolve Grid Software vulnerabilities in the EGI Inspire project. |
EGI Policies and Procedures
See all EGI policies and procedures