EMI JRA1 Data : Glue 2.0 8th October

Present: Elisabetta, Jean-Philippe, Jon, Oliver, Zsombor

Apologies: Christian, Paul


Services concerned are :

  • dCache
  • DPM
  • gLite's FTS & LFC will have to move to GLUE 2.0, but this doesn't need explicit coordination in this forum.
  • ARC will maintain an interest in the group from the client side, but are not responsible for the provision of a relevant service.

We assume an ldap infrastructure, implemented with BDIIs.

According to the original GLUE 2.0 rollout plan (pre-EMI), the services should first publish correctly and then subsequently clients be adapted. The infrastructure is 'GLUE 2.0' ready, and info will be published in a parallel ldap tree.

Validation via reusable gstat 2.0 plugins was seen as a good idea (we may get further input from Paul here though).

All three services use YAIM for configuration, so a standard interface here should be maintained.


dCache, DPM, StoRM:

For the next meeting, supply a list of points for discussion on GLUE 2.0:

  • Problematic mandatory attributes (eg ambiguous, difficult to satisfy...)
  • Candidate optional attributes to be made mandatory
  • Candidate mappings back to existing 1.3 attributes
  • Risks, eg required attributes outside our control (eg UserDomain)

Oliver / Christian:

Clarify UNICORE involvement


Request input from Compute Area


To be discussed.

-- PatrickFuhrmann - 29-Oct-2010

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-10-29 - PatrickFuhrmann
    • 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-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback