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.

PROC08 Management of the EGI OPS Availability and Reliability Profile

From EGIWiki
Revision as of 10:36, 17 March 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


Title Modification of the set of AVAILABILITY tests
Version 1.0
Document link https://wiki.egi.eu/wiki/PROC08_Modification_of_the_set_of_AVAILABILITY_tests
Last modified 16:18, 16 March 2011 (UTC)
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Person E. Imamagic
Document Status DRAFT
Approved Date specify
Procedure Statement This document specifies the procedure for modifying the set of AVAILABILITY tests, i.e. of those tests whose results affect the computation of the monthly Availability and Reliability statistics.

Overview

The purpose of this document is to clearly describe the procedure for modifying the set of AVAILABILITY tests, i.e. of those tests whose results affect the computation of the monthly Availability and Reliability (A/R) statistics.

Detailed description of probes and tests can be found on the SAM Tests page.

Scope

This procedure is applicable to the set of AVAILABILITY tests which are run under OPS VO and its range is global, as they are applied to all Resource Centres in EGI project. These tests are used in the official EGI ACE profile used for generating monthly A/R reports.

This procedure does not apply to availability/reliability statistics calculated for other VOs (e.g. user communities, national operations VOs).

This procedure does not apply to modifications which have already been agreed with the SAM team:

  • including CREAM-CE results
  • switching from the old SAM CA probe to the new one
  • switching from the old SAM ARC probes to Nagios ones.

Entities involved in the procedure

  • Applicant. The Applicant submits a request for adding a new AVAILABILITY probe.
  • Chief Operations Officer. OTAG is the Operations Tool Advisory Group who is responsible of processing the request and of accepting/refusing it with the consensus of the Resource Infrastructure Providers, and is chaired by the person in charge of coordinating tool development activities in EGI.
  • SAM Product Team. The SAM Product Team is responsible of scheduling, integrating and releasing the accepted probes.


Prerequirements

This procedure requires usage of ACE system for generating monthly A/R statistics. The procedure does not cover GridView system which is currently used. The critical feature which ACE supports and GridView lacks is definition of multiple profiles for A/R statistics. Detailed information about ACE system can be found on the following link: https://tomtools.cern.ch/confluence/display/SAM/ACE.

In case when modification request includes addition of new tests, each test MUST first go through following procedures:

Two procedures above assure that the new tests are included in SAM release, deployed on all NGI SAM instances and accepted by operators.

Request

  • Everyone is allowed to submit the request for modifying the set of AVAILABILITY tests.
  • The procedure requires generation of two A/R reports for comparison (find details below) and therefore only one request will be processed at a time. Order of processing requests will be defined by the SA1 activity leader.

Procedure

Step Action on Action
1 Requester Opens a RT ticket (https://rt.egi.eu/rt/index.html) in queue noc-managers.
Subject: Request for adding/removing XXX(,YYY,...) test(s) from the set of AVAILABILITY tests

We would like to request adding/removing XXX(,YYY,...) test(s) from the set of AVAILABILITY tests

Prerequisite data:
* name of SAM test(s):
* name of service on which the test runs:
* link to documentation page:
* motivation (which part of the infrastructure will be improved with the new probe
 or description of users' problems which will be avoided in future - provide list
 of GGUS tickets is possible)
2 SA1 activity leader Schedules presentation of the new probe at the next possible OMB meeting.
3 Requester Explains the reason for modifying set of AVAILABILITY tests
4 (*) SA1 activity leader Opens a ticket in JIRA system (https://tomtools.cern.ch/jira/secure/) requesting creation of new ACE profile with modified set of AVAILABILITY tests.
5 (*) ACE team ACE team creates the new ACE profile.
6 SA1.8 task staff For the following one month two A/R reports are generated. SA1.8 task staff compares the figures and presents them at the next OMB meeting.
7 OMB If the A/R statistics generated with the new A/R profile are satisfactory OMB approves the modification
8 (*) SA1 activity leader Opens a ticket in JIRA requesting that the new A/R profile becomes the official for EGI.
9 SA1 activity leader Broadcasts the modification to all relevant parties (i.e. noc-managers, inspire-sa1). Closes the initial RT ticket.

(*) - These steps depend on the procedure for creating new profiles which will be defined by the ACE team once the ACE is in production. Steps defined here have been provided by the ACE team. This procedure will be updated if any change occurs.

Revision History