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 "Documentation"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
|} | |} | ||
---- | ---- | ||
{| | |||
The EGI [[Operations Manuals]] are technical documents that provide approved guidelines on how to accomplish a given task. These documents are periodically reviewed, and need to be followed by all partners (as opposed to a best-practice documents that provide optional guidelines). | |Operations Manuals | ||
| The EGI [[Operations Manuals]] are technical documents that provide approved guidelines on how to accomplish a given task. These documents are periodically reviewed, and need to be followed by all partners (as opposed to a best-practice documents that provide optional guidelines). | |||
|- | |||
The EGI [[Operations Best Practices]] are technical documents providing reference information on how technical operational tasks can be addressed. A best practice can be optionally adopted by a partner if deemed suitable, the guidelines provided are '''optional'''. Nevertheless a best practice is periodically reviewed, and if relevant to grid middleware deployment it is formally approved by the relevant Technology Provider. | |Operations Best Practices | ||
|The EGI [[Operations Best Practices]] are technical documents providing reference information on how technical operational tasks can be addressed. A best practice can be optionally adopted by a partner if deemed suitable, the guidelines provided are '''optional'''. Nevertheless a best practice is periodically reviewed, and if relevant to grid middleware deployment it is formally approved by the relevant Technology Provider. | |||
A Best Practice is contributed on a voluntary basis by EGI partners to share knowledge and experience. | A Best Practice is contributed on a voluntary basis by EGI partners to share knowledge and experience. | ||
|- | |||
|Operational Procedures | |||
|EGI [[Operational Procedures]] are prescriptive document 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. The intructions providewd by a procedure are mandatory. Applicable areas: | |||
*Ticket management | *Ticket management | ||
*Operations Center Management | *Operations Center Management | ||
*Availability and monitoring | *Availability and monitoring | ||
|- | |||
|Securiy Procedures | |||
|Security procedures are prescriptive documents that define processes specific to operational security. Security procedures | |||
Refer to [[EGI_CSIRT:Incident_reporting|Incident Reporting Procedure]] | Refer to [[EGI_CSIRT:Incident_reporting|Incident Reporting Procedure]] | ||
|} | |||
===[[Operational FAQ]]=== | ===[[Operational FAQ]]=== | ||
Revision as of 15:04, 14 February 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 |
Welcome to the EGI Operational Documentation pages, whose purpose is to guide EGI operations at different levels: site management, NGI operations management (regional Operator on Duty - ROD) and EGI operations (Central Opeartor on Duty - COD).
| Coordinator: | Vera Hansper (CSC) |
| Contact information: | operational-documentation (at) mailman.egi.eu |
| Operations Manuals | The EGI Operations Manuals are technical documents that provide approved guidelines on how to accomplish a given task. These documents are periodically reviewed, and need to be followed by all partners (as opposed to a best-practice documents that provide optional guidelines). |
| Operations Best Practices | The EGI Operations Best Practices are technical documents providing reference information on how technical operational tasks can be addressed. A best practice can be optionally adopted by a partner if deemed suitable, the guidelines provided are optional. Nevertheless a best practice is periodically reviewed, and if relevant to grid middleware deployment it is formally approved by the relevant Technology Provider.
A Best Practice is contributed on a voluntary basis by EGI partners to share knowledge and experience. |
| Operational Procedures | EGI Operational Procedures are prescriptive document 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. The intructions providewd by a procedure are mandatory. Applicable areas:
|
| Securiy Procedures | Security procedures are prescriptive documents that define processes specific to operational security. Security procedures
Refer to Incident Reporting Procedure |
Operational FAQ
Documentation Contacts
- Notice Board
- Documentation Team
Internal area
- Procedures ready for approval: no procedures at the moment are waiting for OMB approval.
- Drafts: Operations documentation authors area