KJRA1.2 Number of Interoperable Interface Usage

Legend:
x(y): x - achieved; y -target

Trends available from Q3

What does it mean when component A has adopted standard B?
  • Some examples around the Technical Objective Compute 1 (GLUE2 Integration)
    • For Q2 it was expected (i.e. target (1) ) that A-REX is able to exchange GLUE2 information via an interoperable interface with the BDII component - That was achieved in Q2: 1(1)
    • For Q2 it was expected (i.e. target (1) ) that also CREAM is able to exchange GLUE2 information via an interoperable interface with the BDII component - That was not achieved in Q2: 0(1)
    • For Q2 it was not expected for VOMS to exchange GLUE2 information via an interoperable interface with the BDII component and is currently also not planned within EMI

What does it mean when components A, B have interoperable interfaces?

  • Some examples around the common adoption of the OGF Storage Resource Manager (SRM) interface
    • DPM (component A), StoRM (component B), and dCache (component C) all adopt the SRM interface and thus any SRM-compliant client (e.g. ARC* client and LCG_Utils) can access these three systems (given correct security setups are in place) with the same standardized protocol.

Year 1

Q1: Not reported

Q2 Q2

Service/component UCC
(BES client)
ARC* Client
(BES client)
ARC* Client
(GLUE2.0 client)
ARC* Client
(SRM client)
LCG_Utils
(SRM client)
LCG_Utils
(GLUE2.0 client)
BDII
(GLUE2.0)
A-REX (BES) 1(1) 1(1)         1(1)
ARGUS (SAML)              
BDII (GLUE2.0)     1(1)     1(1)  
CREAM (GLUE2.0)             0(1)
dCache (SRM)       1(1) 1(1)    
DPM (SRM)       1(1) 1(1)    
FTS              
StoRM (SRM)       1(1) 1(1)    
UNICORE Compute (BES) 1(1) 1(1)         0(1)
UVOS (SAML) 1(1)            
VOMS (SAML) 1(1)            
WMS (GLUE2.0)             0(1)
Total 4(4) 2(2) 1(1) 3(3) 3(3) 1(1) 1(4)
NB:
GLUE2 deviation is not considered crucial issue; KPI target expected to be reached in year 1.
The use of the standard X.509 is omitted here since it is the baseline for all components and thus relevant for each component.
Q3 Q3

Service/component UCC
(BES client)
ARC* Client
(BES client)
ARC* Client
(GLUE2.0 client)
ARC* Client
(SRM client)
LCG_Utils
(SRM client)
LCG_Utils
(GLUE2.0 client)
BDII
(GLUE2.0)
A-REX (BES) 1(1) 1(1)         1(1)
ARGUS (SAML)              
BDII (GLUE2.0)     1(1)     1(1)  
CREAM (GLUE2.0)             0(1)
dCache (SRM)       1(1) 1(1)   1(1)
DPM (SRM)       1(1) 1(1)   1(1)
FTS              
StoRM (SRM)       1(1) 1(1)   1(1)
UNICORE Compute (BES) 1(1) 1(1)         1(1)
UVOS (SAML) 1(1)            
VOMS (SAML) 1(1)            
WMS (GLUE2.0)             0(1)
Total 4(4) 2(2) 1(1) 3(3) 3(3) 1(1) 5(7)
NB:
GLUE2 deviation is not considered crucial issue; KPI target expected to be reached in year 1.

*Trend Diagram Q2->Q3 KJRA12-Q2Q3-Trend.png

Tracking

2011-03-04 : Morris add additional remarks to the Q2 KPIs as well as answers to some clarifiying overall questions

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng KJRA12-Q2Q3-Trend.png r1 manage 13.6 K 2011-05-04 - 23:55 UnknownUser  
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2011-05-05 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI 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