You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Document control

AreaEGI Federation Operations
Procedure status

DRAFT

OwnerAlessandro Paolini 
ApproversOperations Management Board
Approval status

APPROVAL REQUIRED

Approved version and date


Statement

This document specifies the procedure for modifying the EGI OPS Availability and Reliability profile

Next procedure reviewupon request

Procedure reviews

The following table is updated after every review of this procedure.

DateReview bySummary of resultsFollow-up actions / Comments








Table of contents

Overview

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. A change in the OPS Availability and Reliability profile affects the computation of the monthly Availability and Reliability statistics of all EGI Resource Infrastructures and Resource Centres.

Definitions

Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

  • The key words Profile, Metric, Probe and Test are defined in the ARGO page.
  • List of Availability and Reliability tests: ARGO_MON_CRITICAL

Scope

This procedure is applicable to the EGI OPS Availability and Reliability profile. Any change applied is global, as it has effects on all EGI Resource Centres. The ARGO compute engine (CE) uses profiles to generate monthly Availability and Reliability reports.

This procedure is NOT applicable to VO-specific Availability and Reliability profiles used by non-OPS VOs (e.g. user communities, national operations VOs, etc.).

Entities involved in the procedure

  • Applicant. The Applicant submits a request for changing the EGI OPS profile. Anybody is allowed to submit the request. The request is submitted to the respective Operations Centre, who after acceptance, forward it to the Operations Management Board (OMB) for discussion.
  • Operations Centre. The entity associated to EGI that is responsible of delivering local operational services to a Resource Infrastructure Provider. In order to contribute resources to EGI a Resource Infrastructure Provider must be associated to an Operations Centre.
  • Resource Infrastructure Operations Manager. Represents the respective Resource Infrastructure within the OMB.
  • EGI Operations team. Team coordinating EGI Infrastructure.
  • ARGO Team. The ARGO Team is responsible of scheduling, integrating and releasing probes.

Triggers

Steps

Step# ResponsibleActionPrerequisites, if any















  • No labels