GLUE2.0 WG Minutes

Meeting Thu 13th January, 16:30 CET

Agenda

  • Progress update & issues
  • Next steps
    • testbed
    • validation
  • EMI Technical Conference
  • AOB

Meeting minutes:

PRESENT

Elisabetta, Michel, Oliver

NOTES

Elisabetta reported that she had created a script similar to the one for GLUE 1.3 for STORM and had updated yaim scripts to handle the configuration.

Michel reported he was in the process of adapting dpm-listspaces to handle GLUE 2.0.

Oliver reported that the Infrastructure Area would soon be providing gstat 2.0 probes to test basic GLUE 2.0 publishing

EMI Technical conference - Agreed to have two separate abstracts for the WG and for STORM. Noone volunteered to give the WG one so Oliver will do it.

The FAQ has been updated with the result of discussions on which rpms are required to publish GLUE 2.0 and how to handle a GLUE 1.3 GlueSA with N>1 GlueVOInfo entries.

Elisabetta will contact local EMI SA2 resources to get an instance of STORM installed with GLUE 2.0 support

Michel will contact Oliver when dpm-listspaces is ready (by 21st Jan) and Oliver will udpate the DPM on the EMI testbed appropriately.

Meeting 19th November 2010, 10:00 AM CEST

Agenda

  • Minutes from last meeting
  • Actions
    • Everybody to review again the attributes and indicate if there are any which the WG should declare as mandatory
    • Paul to write a one paragraph proposal on how to handle the UserDomain * Oliver to ask Patrick to put a general call for input on usecases into his EMI AH presentation.
  • Report from GLUE20 testing phoneconf
  • All Hands
  • AOB

Meeting minutes:

PRESENT

Christian, Elisabetta, Oliver

NOTES

Oliver reported on the GLUE 2.0 testing phoneconf (EMI-wide). 2 main points:

  • PTs will make prototypes available on the shared EMI testbed by the END OF JANUARY
  • Validation via gstat probes was agreed as an approach

The meeting agreed that enough basic questions had been answered to start work on the info providers, and agreed to reconvene at the start of 2011 to check the situation.

Meeting 4th November 2010, 14:00 AM CEST

Agenda

  • Discussion Items
    • problematic mandatory attributes (eg ambiguous, difficult to satisfy...)
    • candidate optional attributes to be made mandatory
    • optional entities
    • candidate mappings back to existing 1.3 attributes
    • risks, eg required attributes outside our control (eg UserDomain)
  • Next Steps

Meeting minutes:

PRESENT

Christian, Elisabetta, Oliver, Paul, Zsombor

NOTES

The Compute Area has been contacted for requirements and at the moment there are none.

The Castor team has been contacted and they will follow progress but have no plans to join the group.

Zsombor asked about the 'EMI technical objectives' which stated there would be a GLUE2.0 enabled client available for EMI1.0. Is this the case, and which one? Oliver to follow up with EMI. (done... no answer yet).

After discussion on how to encapsulate our decisions, in the first instance the group will produce a FAQ style document of decisions, which can be adapted later if necessary. The spec is complete enough that it does not need to be replicated in a second annotated document.

Consequently such decisions are not recorded in the minutes, but at the following URL:

ACTIONS

Everybody to review again the attributes and indicate if there are any which the WG should declare as mandatory

Paul to write a one paragraph proposal on how to handle the UserDomain

Oliver to ask Patrick to put a general call for input on usecases into his EMI AH presentation.

QUESTIONS

How can SEs publish SE specific metadata?

Do we need to allow publishing of the entire managed capacity?

Do we need to extend the 'installed capacity' doc for GLUE2.0?

Meeting 8th October 2010, 10:00 AM CEST

Agenda:

  • Establish the services and clients concerned
  • Discuss how to achieve the objectives:
    • Understand mapping of 1.3->2.0
    • Establish if we can satisfy all obligatory 2.0 attributes
    • Identify any optional attributes we will use
    • Agree on interpretation of attributes if necessary
    • Encapsulation of above in a 'profile'
  • Validation tests
  • Configuration

Meeting minutes:

EMI JRA1 Data : Glue 2.0 8th October

Present: Elisabetta, Jean-Philippe, Jon, Oliver, Zsombor Apologies: Christian, Paul

DECISIONS:

Services concerned are : dCache, DPM, STORM 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.

ACTIONS

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

Oliver:

Request input from Compute Area


This topic: EMI > WebHome > EmiProjectStructure > JRA1 > EmiJra1 > EmiJra1T3Data > EmiJra1GLUE20 > EmiJra1GLUE20Minutes
Topic revision: r3 - 2011-01-18 - OliverKeeble
 
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