GGUS Type of Problem field

GGUS TEAM and ALARM ticket submit forms as of the 2011/09/28 GGUS Release contain the field 'Type of Problem' (ToP) with possible values:

  • Other
  • Databases
  • File Access
  • File Transfer
  • Local Batch System
  • Middleware
  • Monitoring
  • Network problem
  • Storage Systems

This is a subset of ToP values that USER tickets offer. The same exact strings were kept for these values in order to ensure continuity of the searches.

The ToP field values for USER tickets are listed in https://wiki.egi.eu/wiki/GGUS:Type_Of_Problem_Values .

History: GGUS TEAM and ALARM ticket submit forms up to the 2011/09/28 GGUS Release contained the MoU values' drop-down list, which is too generic, but not the 'Type of Problem'. Agreed values for TEAM and ALARM tickets following the T1SCM of 2011/06/16 are:

  • Infrastructure (File transfer/ access, Batch, Monitoring)
  • Storage
  • Databases
  • Network problem
  • Middleware

As decided in the 2011/04/07 T1SCM these values should be:

  1. A subset of the general values for user tickets, in order not to break the interfaces with other ticketing systems and for searches to retrieve all relevant ticket categories.
  2. The same for both TEAM and ALARM ticket categories, because TEAM tickets can be upgraded to ALARM ones and
  3. Related to the Critical services' list (below).
More info in Savannah:117206

Tier0 Critical Services - Generic list - No experiment-specific services included here.

THIS IS THE UP-TO-DATE LIST STATUS OF JANUARY 2013 https://twiki.cern.ch/twiki/bin/view/LCG/WLCGCritSvc

NB!!!!!!!!!THE FOLLOWING IS HISTORICAL DATA - OBSOLETE NOW!!!!! Action from the dedicated meeting on ALARMs' quality tools. See point 5, ACTION_6.

Service ATLAS CMS Alice LHCb Comment by Maria - VOs please answer by editing this page
CERN FTS Y Y N/A Y
CERN LFC service (Master) Y N/A N/A Y
Batch Y Y Y Y
CERN network Campus Y Y Y Y Should we list CERN CC-toPit networking on a separate row?CMS does in doc. 1 below.
CASTOR Y Y Y Y
SRM Y Y N/A Y
Oracle Y Y Y Y
Oracle streams Y Y N/A Y See point 3 in Edit Log below
CERN AFS Y Y Y Y Including the Kerberos service.
Site VO boxes Y Y Y Y computer.operator might not have instructions for the application failing on the box but the experiment experts receive the email notification with the ALARM ticket. Nevertheless, the operators must have instructions for VObox system issues.
xrootd Y N/A Y Y computer.operator might not have instructions but the experiment experts receive the email notification with the ALARM ticket
Totals 11 9 7 11

Useful documents

  1. Prague CHEP 2009 Document used as information source.
  2. CERN IT CASTOR Service Level Description.
  3. Who receives email notification when ALARM ticket to the Tier0 is opened.
  4. GGUS ticket routing to the Tier0.

Edit Log

  1. Discussed at the 2010/05/20 Tier1 Coordination meeting.
  2. J.Gordon in email 'Maria, perhaps you should label this CERN Critical Services?' - Done.
  3. F.Cavallari in email 'yes I think it is a good idea to add the streaming as a separate line.' - Done.
  4. Discussed at the 2010/05/27 CERN/IT/ES/VOS section meeting with contribution by Jamie S.
  5. This twiki page is the data source for the periodic ALARM tests, e.g. https://savannah.cern.ch/support/?114705
  6. The above test showed lack on response from 'network' services and lack of instructions for the 'VOboxes'.

-- MariaDimou - 20-May-2010

Edit | Attach | Watch | Print version | History: r18 < r17 < r16 < r15 < r14 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r18 - 2013-11-06 - MariaDimou
 
    • 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-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback