Operational Procedures

The Operations manual was split into three different parts to cover the transition period from COD to ROD

The three different parts of the Operations Manual can be found in the following links or on EDMS:

This version was released on 9th April 2010

Operational Procedures for ROCs and Sites

Operational Procedures for ROD

Operational Procedures for CCOD

Download the most recent official version in PDF format:

Pole 2

Pole 2 - Operational Documentation Authors area

Operations Best Practices

Operations Best Practices

Operations Dashboard HOW TO and training

Operational Use Cases and Status

Operational Use Cases and Status Wiki Format

This document describes the operational use cases detected by the CODs. It also gives their status in term of GGUS/Savannah ticket and the place this operational use case has been raised. The document is updated by the COD lead team at least once a week and the use case should be discussed during the WLCG Weekly Operation meeting. It also have to be presented at each ROC Managers Meeting by a COD representative.

Security Incident Handling and Response Guide

Updated Link

This document is intended for Grid site security contacts and site administrators. It is expected that this policy document will be supplemented by additional information concerning Incident Response procedures published on project websites.

OAG Procedures and Policy Report 13/6/2006

This document describes mandate, composition, procedures, and tools of the Operations Advisory Group (OAG) of EGEE, either planned or in place. The OAG is a coordination group between the activities NA4 (Applications) and SA1 (Operations). This could be important for VO managers, especially of new VOs, and also for site administrators as well as ROC managers.

VOMS Admin 16/3/05

The VOMS Admin service is a web application providing tools for administering member databases for VOMS, the Virtual Organization Membership Service. VOMS serves as a central repository for user authorization information, providing support for sorting users into a general group hierarchy, keeping track of their roles, etc. Its functionality may be compared to that of a Kerberos KDC server.

It provides an intuitive web user interface for daily administration tasks, and a SOAP interface for remote clients. (The entire functionality of the VOMS Admin service is accessible via the SOAP interface.) The Admin package includes a simple command-line SOAP client that is useful for automating frequently occuring batch operations, or simply to serve as an alternative to the full-blown web interface. It is also useful for bootstrapping the service.

Integrate a new Virtual Organization 27/7/04

This document proposes a procedure for both acceptance and deployment of a new VO to the EGEE infrastructure.

It contains the organizational and technical aspects of these procedures.The target audience of this document is the SA1 people, in particular, the representatives of RCs, ROCs, CICs and OMC.

Virtual Organization Registration Procedure 22/5/06

This document lists the necessary steps a Virtual Organisation (VO) should take in order to get registered with and integrated into the EGEE infrastructure.

Virtual Organization Security Policy 2/10/05

This policy defines a set of responsibilities placed on the members of the VO and the VO as a whole through its managers. It aims to ensure that all Grid participants have sufficient information to properly fulfil their roles with respect to interactions with a Virtual Organisation (VO). This policy does not address the process by which disputes between Grid participants are resolved. It is expected that VO and Grid management bodies will agree appropriate mechanisms through which such disputes can be resolved.

Useful Links

Grid Log Retention Guidelines 14/3/06

The current minimal Log Retention policy states that log information must be kept for at least 90 days. This page intends to details a sample implementation of this policy. Job submission will normally progress from a User Interface (UI) machine, through a Resource Broker (RB) to a Computing Element (CE) and hence to the compute resource (usually a batch system). In some cases the RB is not used and the UI submits the job directly to the CE. Data access is through a Storage Element (SE) service and may be initiated directly from the UI or from a task executed on the compute resource.

Sources of trace information for the LCG CE June 2005

Security Service Challenge level 1 (SSC_1) 7/9/06

Security Service Challenge level 1 (SSC_1) challenges the Workload Management System (WMS) on the Grid: Resource Broker (RB) and Compute Element (CE). The goal of the LCG/EGEE Security Service Challenge (SSC), is to investigate whether sufficient information is available to be able conduct an audit trace as part of an incident response, and to ensure that appropriate communications channels are available.


Grid Certification Guide 15/3/05

Middleware Documentation

CVS User Guide ok

Help Using of CVS areas in LCG. This documentation must be read by all LCG deployment group and by developer working on LCG development.

gLite3 User Guide 17/01/07

This document gives an overview of the gLite 3.0 middleware. It helps users to understand the building blocks of the Grid and the available interfaces to the Grid services in order to run jobs and manage data.

This document is neither an administration nor a developer guide. It is addressed to WLCG/EGEE users and site administrators who would like to work with the gLite middleware.

LCG-2-UserGuide Aug 2005

This document gives an overview of the main characteristics of the LCG-2 middleware, which is being used for EGEE. It allows users to understand the building blocks and the available interfaces to the GRID tools in order to run jobs and manage data. This document is neither an administration nor a developer guide.

It is addressed to users and site administrators of EGEE who would like to work with the LCG-2 Grid middleware.

LCG2-Manual-Install 23/11/06

This document is addressed to Site Administrators in charge of middleware installation and configuration.

It is a generic guide to manual installation and configuration for any supported node types. It provides a fast method to install and configure the gLite middleware on the various node types (WN,UI, CE, SE ...).

LCG2-Manual-Upgrade 3/5/06

This document is addressed to Site Administrators in charge of middleware installation and configuration.

It is a generic guide to the manual upgrade procedure for the various node types (WN, UI, CE, SE etc.) on SLC3 and binary compatible OSes. It refers to the upgrade between the latest middleware release and the previous one.

LCG2-Site-Setup 31/1/06

This document describes the process of setting up and registering a grid site using the middleware packaged by LCG.

This middleware represents the current middleware stack used in the LCG-2 and EGEE production grid. This information is relevant for site managers or sysadmins that want to setup a EGEE/LCG-2 production site or upgrade their site to the latest release.

LCG2-Site-Testing 15/05/06

This is a collection of basic commands that can be run to test the correct setup of a site.These tests are not meant to be a replacement of the test tools provided by LCG certification team. They are instead a collection of quick and non invasive functional tests suitable to be run in order to be sure that the site configuration has been correctly performed. The tests in this chapter should enable the site administrator to verify the basic functionality of the site.

LCG-Midleware-developers-guide 3/9/04

This document is a guide for anyone developing or modifying code for LCG. This guide is directly derived from the European Datagrid Developer�s Guide. The LCG version differs to suit the requirements of LCG and is more concise. The main objective of this guide is to define the procedures used by LCG for software development to ensure that the software produced meets quality required for a production system. This guide focuses on the basics in order for it to be easily followed, flexible and applicable to other projects. This guide should also be an example to anyone producing software for LCG demonstrates what is expected in matters of quality.

Experiment Software Installation in LCG-2 22/7/05

About the installation of experiments software on LCG-2 sites.

Maui-Cookbook for LCG V1.1

This document introduces the Maui advanced job scheduler in the context of LCG. It also shows how Maui is being used at two sites having different approaches: the English Rutherford Appleton Laboratory (RAL) and the Dutch National Institute for Nuclear and High Energy Physics (NIKHEF).

R-GMA Server User Guide 13/6/05

The R-GMA server is a Java servlet-based web application which provides the Consumer, Producer,Registry and Schema services for the R-GMA distributed information and monitoring system. The server is designed to be run within a servlet container such as Jakarta Tomcat.

Tomcat versions 4 and 5 have been tested, however other versions or other servlet containers may also work. This document describes the servlet-based implementation of the R-GMA server.

R-GMA Command Line Tool 2/11/05

The R-GMA command line tool provides simple shell-like access to the R-GMA distributed information and monitoring system. R-GMA uses a relational model to publish and query information using the SQL language. This document describes the R-GMA command line tool.


The LCG File Catalog (LFC) is a high performance catalog provided by LCG. This document describes the LFC architecture and implementation. It also explains how to install the LFC client as well as the LFC server (version >=1.6.3.) for both My SQL and Oracle backend.


Grid tutorial 1/9/04

This document leads you through a number of increasingly sophisticated exercises covering aspects of job submission, data management and information systems. It is assumed that you are familiar with the basic Linux/UNIX user environment (bash, shell etc.) and that you have obtained a security certificate providing access to the LCG-2 testbed. This document is designed to be accompanied by a series of presentations providing a general overview of Grids and the LCG tools. Solutions to all the exercises are available online. We do not give exact host names of machines in the testbed since they change over time.

Infrastructure Planning Guide 16/12/05

This document is a summary of the experience and knowledge gained during the building of the EGEE grid infrastructure. The document is intended to explain some of the decisions and choices made in planning,deploying, and operating the infrastructure, and should be helpful to others who consider building grid infrastructures or participating in existing grids. It is not intended to be definitive, but rather to explain the issues and the experience with the hope that others can benefit.


Monitoring and Alarm Systems 17/9/04

This document is an initial assessment of the current CIC activity in monitoring and covers five monitoring tools:

GPPMON, GRIDICE, GSTAT, NAGIOS and Real Time Grid Monitor.

Inventory of Operation Tools, Procedures and Gap Analysis 8/6/06

This document contains the inventory of operations� tools, procedures, and gap analysis.

Goc_db details Are these contact details up to date?

Web Site

Accounting and Reporting Web Site Publicly Available 19/1/05

This document describes the �Accounting and Reporting Web Site� for deliverable DSA1.3 for SA1 Operations Activity. This is a software deliverable, not a document deliverable. This deliverable provides a brief description of the software processes set in place for the collection of accounting data and for the presentation of this data by means of a publicly accessible web page.

Adding a user in the access list 15/9/04

This document provides information on how to add a user in the author list in the documentation system.

Changing the contents of the VO table in the CIC portal 17/2/05

This document provides information on how to change the content of the VO tables in the CIC portal.

Creating a private web space for a user 17/9/04

This document provides information on how to create a private web space for a user in the documentation system.

Locally changing a file 2/9/04

This document provides information on how to change the contents of a file in the documentation system.

Logging on with WebDAV 2/9/04

This document provides information on how to logon to the documentation system with WebDAV using Internet Explorer on the Windows platform.

Remotely changing a file 2/9/04

This document provides information on how to change the contents of a file in the documentation system.

SA1 Documentation System 2/9/04

This document provides information on how to browse the contents of a file in the documentation system.



Operational Documentation Per ROC


Configuration of Virtual Organizations 20/1/06

This document provides a detailed description of the so called VO management feature implemented in the gLite configuration system. It provides the implementation description, use-cases and extensive examples for any gLite middleware administrator doing modifications in the default VO management configuration provided in the release. It contains VO management implementation details useful for understanding of the VO management functionality and also hints and examples for advanced and expert configuration. Document assumes good knowledge of the gLite configuration model (configuration procedure, schema, etc.) and basic knowledge of XML.

-- PeteGronbech - 2009-09-02

Edit | Attach | Watch | Print version | History: r33 < r32 < r31 < r30 < r29 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r33 - 2011-06-16 - VeraHANSPERExternal
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback