CCRC'08 Service Map

Overview

The CCRC'08 ServiceMap is a tool for displaying different aspects of the service readiness of the WLCG Computing Infrastructure. the list of services are those provided by the WLCG experiments.

There are currently three different view components:

  • Service Readiness - An evaluation of the service against a list of common deployment questions
  • Service Availability - Availability of a service
  • Experiment supplied data - this is data provided by the experiment frameworks to show their view of different aspects of the service e.g. reliability, throughput, usage, etc...

Components

Service Readiness

The Service Readiness map is designed to show how ready a service by looking at the maturity of the software, the service in general in terms of documentation, process and procedures and the specific deployment at a site. Each question is scored between 0 and 1 (or - if not relevant), and the overall readiness is the average of the individual questions. The questions are in three sections, each dealing with a different aspect:
  • Software Readiness
  • Service Readiness
  • Site Readiness

Software Readiness

Question Comments
High-level description of service available? with architecture diagam
Middleware dependencies and versions defined? OS deps, M/W deps, platforms supported
Code released and packaged correctly? Repository + Tagging process, rpms/tarballs
Certification process exists?  
Automatic Configuration code exists? e.g. Yaim, NCM, …
Admin Guides available? Installation, monitoring, problem determination

Service Readiness

Question Sorted descending Comments
Support chain defined (2nd/3rd level)?  
Problem determination procedure documented  
Monitoring criteria described?  
Disk, CPU, Database, Network requirements defined?  
Backup/restore procedure defined?  

Site Readiness

Question Comments
Suitable hardware used  
Monitoring implemented  
Test environment exists  
Problem determination procedure implemented  
Automatic configuration implemented  
Backup procedures implemented and tested  

Service Availability

The Service Availability map shows availability for the VO Critical services. This currently uses either SAM or SLS for the actual results gathered. There is a single configuration file which controls what is displayed in the gridmap. It is a tab separated file, which is shown below:
VO      Service Rank    Comment Tier    Data Quality    Data Source     Data Query      Data Tier
LHCb    CERN VO boxes   10              0       no results for VO       SAM     VOBOX   T0
LHCb    CERN LFC service        10              0       no results for VO       SAM     LFC     T0
LHCb    VOMS proxy service      10                      no results for VO       SAM     VOMS    T0
LHCb    T0 SE   7               0               SLS     CASTORLHCB      T0
LHCb    T1 VOboxes      7               1       no results for VO       SAM     VOBOX   T1
LHCb    SE access from WN       7               0,1                             T0,T1
LHCb    FTS channel     7       both CERN to/from T1 & inter T1 0,1             SAM     FTS     T0,T1

The important field here are :

Field Usage
VO Which VO map to show this entry in
Service The text shown in the box
Rank The size of the box
Data Source Where does the data come from - SAM or SLS
Data Query The query to use to the source -e.g. SAM node type, or SLS metric name
Data Tier 0, 1,2 - defines it it shows when you select a specific site

The file is stored in the WLCG Grid Monitoring SVN Repository: https://www.sysadmin.hep.ac.uk/svn/grid-monitoring/trunk/ccrc08/config/datafiles. To update the map, you should modify the file servicelist.txt. This is automatically syncronized with gridmap.cern.ch every five minutes.

Experiment View

Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2008-04-24 - JamesCasey
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback