KJRA1.2 Number of Interoperable Interface Usage

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.

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.

NB:
GLUE2 deviation is not considered crucial issue; KPI target expected to be reached in year 1.

*Trend Diagram Q2->Q3