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.

Documentation

From EGIWiki
Revision as of 15:39, 14 February 2011 by Tferrari (talk | contribs)
Jump to navigation Jump to search
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

Manuals The EGI Operations Manuals are technical prescriptive documents that provide 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).

Contact: operational-documentation-manuals[at]mailman.egi.eu

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 preliminary approved by the relevant Technology Provider.

A Best Practice is contributed on a voluntary basis by EGI partners to share knowledge and experience. Contact: operational -documentation-best-practices[at]mailman.egi.eu

Procedures 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. The intructions providewd by a procedure are mandatory. Applicable areas:
  • Ticket management
  • Operations Center Management
  • Availability and monitoring
Security Procedures Security procedures are prescriptive documents that define processes specific to operational security in the areas of:
  • Security Incident Handling
  • Vulnerability Issue Handling
FAQs Frequently Asked Questions are question/answer documents providing information on specific technical areas. The FAQ provides a high-level overview of the issue and collection of links for futher investigation
Training Guides under development

Documentation Contacts

  • Notice Board
  • Documentation Team

Internal area

Resources