DILIGENT meeting with NA4

Wednesday 12 Apr 2006, 16:00 → 18:00 Europe/Zurich

Meeting with NA4 (#53), Geneva, 12th April Objective: Meeting with NA4 leader Cal Loomis to discuss the work done by TCG, the work done by DILIGENT in the TCG workgroups, DILIGENT requirements for gLite3.0, the new organization of NA4 and the need for DILIGENT MoU in the context of EGEE-II Participants:  Pedro Andrade  Roberta Faggian Marque  Charles Loomis (NA4 activity leader and DILIGENT representative in TCG) Agenda:  Presentation of DILIGENT requirements  Outcome of last TCG meetings  EGEE development and support plans  Need for a DILIGENT-EGEE MoU Requirements presented: Besides the requirements being analyzed by the TCG workgroups, with the introduction of new components in gLite 3.0 also new requirements were identified by DILIGENT. These requirements were explained to C. Loomis:  web service interface for LFC  java API for LFC  java API for the LCG utilities  possibility to use R-GMA (instead of BDII) to publish or retrieve information about DPM and LFC from the LCG utilities Results: 1) C. Loomis took note of DILIGENT major requirements and discussed possible solutions for the usage of R-GMA to retrieve information about DPM and LFC from the LCG utilities. Since for know this task is impossible, C. Loomis proposed to have both information system running, continue to use R-GMA as the default IS and automatically duplicate the information in BDII using existing gLite tools. 2) C. Loomis informed that there is not a clear procedure for which the project could be informed about the timeline for implementation of TCG resolutions since this is in the hands of the single activities. 3) C. Loomis clarified on EGEE plans for the future: no new functionality will be developed since focus will be given to stability of the current system. Minor features could be implemented if required by the project. 4) C. Loomis informed on the existence of a procedure by which new external components could be integrated into the gLite software stack. This means that if DILIGENT identifies external components which could provide important functionality, these components could be submitted to this integration process. 5) C. Loomis clarified on the level of support that will be provided to the different gLite components. 6) C. Loomis explained about the new EGEE procedure for interaction with user VOs. A VO should register though a Web interface to become an EGEE registered VO and get access to training and test infrastructure. A VO could ask for specific support and access to production infrastructure. In this case the VO request will be submitted to approval and the VO will become a selected VO. Specific collaboration and support condition could be agreed in a Memorandum of Understanding (MoU). 7) It was agreed that a MoU could be useful for DILIGENT to agree on the following aspects: integration of DILIGENT with EGEE production infrastructure, needed support from EGEE operation team, resources needed and provided by DILIGENT, possible EGEE training to be provided on specific areas and joint technical meetings to discuss about DILIGENT specific design choices which involve exploitation of gLite functionalities, gLite software short and long term support needs from DILIGENT.