DILIGENT previous meetings

Sunday 1 Jan 2006, 08:00 → 18:00 Europe/Zurich

08:00 → 09:00 TCG

11/11/05 Plan for convergence towards a single EGEE middleware stack called gLite status quo: SA1 is preparing release LCG-2.7.0 which should be released during November, 2005. JRA1 is preparing release gLite 1.5.0 which should be released at the end of December, 2005. goal: converge to a single EGEE middleware stack called gLite 3.0.0 process: Based on the components available in gLite 1.5.0 and LCG-2.7.0 the TCG, which will start its operation on November 9, 2005, will produce a list of components that should be released as gLite 3.0.0. This list will be produced by the end of November, 2005. During November and December the SA1 and JRA1 integration and release teams will work on convergence of their systems, focusing on the planned components for gLite 3.0.0. By the end of January, 2006 an integrated release candidate for gLite 3.0.0 will be produced. During February 2006 the release candidate will be tested and certified (which may result in the exclusion of certain components) with the goal to release gLite 3.0.0 publicly by the end of February 2006. The whole process will be monitored by the TCG. other points: It is envisaged that after gLite 1.5.0 and LCG-2.7.0 there are no further independent releases (unless critical issues need to be resolved immediately) but the focus will be on gLite 3.0.0. Effectively, the work on gLite 3.0.0. is bootstrapping the work of SA3. Components of gLite 1.5.0 and LCG 2.7.0 that will not be part of gLite 3.0.0 may continued to be supported by their providers (and thus be considered for later inclusion by the TCG) but the EGEE testing and integration efforts are solely focused on gLite 3.0.0.

09:00 → 10:00 NA4 meeting

30/11/05 Vincet Breton 1. Procedure/protocol on how DILIGENT becomes part of NA4. (Status of DILIGENT MoU) We agree that DILIGENT looks at the MoU signed by Computational Chemistry and expresses its own requests for collaboration with EGEE activities. NA4 will circulate the MoU to the other EGEE activities so that they can give their feedback. 2. On requirements PTF database is available. Although it has not been active for a couple months, it is still accessible for update. Requirements are contributed by Diligent to the PTF database by Pasquale Pagano. 2.1 Who to contact in NA4 w.r.t. requirements Requirements are going to be used by TCG working groups. The channel for contribution to TCG working groups is through Charles Loomis and Massimo Lamanna. 2.2 NA4 review of the already submitted DILIGENT requirements Limited resource within NA4 to review external projects requirements 2.3 Procedure on monitoring/follow-up of submitted requirements Through the TCG working groups 2.4 Procedure on submitting new requirements Requirements are contributed by Diligent to the PTF database by Pasquale Pagano. 3. On collaboration & events 3.1. Who to contact in NA4 w.r.t. events? - Participation in upcoming events - Catania in Jan 2006, Users' Forum in March 2006. 3.2 Collaboration tools - twiki, mailing list 4. NA4-related activities - who to contact/ how to participate/how to get involved 4.1 TCG 4.2 TF - DILIGENT TF? 4.3 Workgroups - Short Deadline Jobs - Database Access on the Grid 5. Cal Loomis' requirements Discussion with Donatella but lack of use cases Specify one or two use cases in the Memorandum of Understanding Deployment of Diligent VO on the PPS Follow-up of MoUs: Florence Jacq, with the help of Roberto Barbera, Charles Loomis and Massimo Lamanna Till the end of EGEE, Diligent will be integrated into NA4 generic. Florida Estrella 1) MoU – Memorandum of Understanding Must be signed between DILIGENT & NA4 currently NA4 has MoUs with user communities, groups deploying applications on the EGEE infrastructure, groups asking for resources MoU for DILIGENT will serve as a collaboration document, it might also serve as a model or template for the new EU projects. DILIGENT is the 1st collaborating project with NA4. MoU is a formal agreement. It should include use cases (what DILIGENT wants to do w.r.t. the EGEE middleware), milestones & plans. Ideally 1-2 usecases in the next 6-12 months. It should include requirements that need to be addressed, and by when. It should also include the manpower implications on EGEE. It should include all activities of EGEE that DILIGENT will make use of – JRA1, SA1, NA2, NA3, NA4, etc. At the moment, DILIGENT does not foresee any manpower implication on NA4. The MoU may be submitted to the EU, perhaps as an appendix for the WP3.1 deliverable. Florence Jacques of NA4 will followup on the DILIGENT MoU. DILIGENT should look at the Computational Chemistry MoU sent by Roberto Barbera. DILIGENT will be part of the NA4-Generic Applications group, led by Roberto. 2) Requirements Person to contact w.r.t. requirements is Cal Loomis charles.loomis@cernNOSPAM.ch. The requirements database is quite big and a little disorganized. The requirements database is still open (and not dead!). The TCG and its working groups (WG) are responsible for arranging/organizing/prioritizing/addressing there requirements into working groups. There are 2 “blessed” WGs so far – short deadline jobs and medical metadata management. DILIGENT is interested in joining the short deadline jobs WG.

10:00 → 11:00 UIG meeting

25/11/05 Present: Joanne Barnett David Ferguson Marcel Soberman Jim Buddin Pedro Andrade Action 1 - ALL Set-up monthly UIG teleconferences. Proposed dates 12th of each month. Next meeting 12 December at 12 CET (details of telecon to follow). Following Pisa it appears there are a number of initiatives taking place elsewhere in the project with regard to documentation which the UIG needs to be aware of. NA3 are implementing a digital library for training material - maybe can be expanded to other areas of the project. NA4 are pursuing expanding their Wiki site. Need input from NA4 to discuss this further. Action 2 - ALL Review the website set-up by TERENA some months ago. If you know of documentation that is missing/out of date let Jim Buddin (jim.buddin@terenaNOSPAM.nl ) know by Wednesday 30 November 2005, 1300 hours (next week). Action 3 - ALL Once updated, the UIG will send an email to the PEB asking for their comments about the site and explaining that the UIG wishes to send an email to the wider EGEE community asking for input (documents missing, best documents etc.). If you have any comments about the email to the PEB, please let Joanne Barnett (barnett@terenaNOSPAM.nl ) know by Wednesday 30 November 2005, 1300 hours (next week). Action 4 - Joanne Barnett/David Ferguson Several people have asked to join the UIG. JB to add Dieter Kranzlmueller (Project Deputy); Steven Burke (GriddPP) and Pedro Andrade (CERN). David to pass Steven Burke's email address to Joanne Barnett

11:00 → 12:00 NA4 technical meeting

13/12/05 Participants: * Pedro Andrade (PA) * Pasquale Pagano (PP) * Charles Loomis (CL) * Birger Koblitz (BK) Five major topics were discussed (actions are described inline): 1. Catalogs: BK reminded that it is not clear yet which catalog will be included in the future gLite 3.x. Up to now DILIGENT has only used and studied the Fireman Catalog (EGEE current supported catalog). DILIGENT should continue the effort of testing FC, trying to understand if FC is capable to answer the DILIGENT needs, specially: * need for local replicas or single centralize service * number/type of calls to FC 2. Short deadlines jobs: There is already one workgroup on this. Currently this group is trying to tune the gLite CE configuration in one site, to work with these type of jobs. This solution is site-specific but it can be applied to all sites. After this work, the plan is to work on the response time of the WMS and LB/RGMA to these type of short jobs. The issue of assigning priorities to jobs will be taken in consideration and it will be integrated in this group or form a new one. CL proposed DILIGENT to join this group. * Action 1: CL will send more information about the group and how to join it. 3. Services certificates: Currently there is no workgroup on this. PP identified two major issues for DILIGENT: allow certificates for services and allow registration of these services in VOMS. BK and CL added that these services must also provide to the resource providers information about the mapping between services and real users. CL mentioned that one BioMed group is already accepting services certificates. * Action 2: CL will ask the TCG for the suitability of having one group of this type. * Action 3: CL will join the interested groups (DILIGENT, BioMed, etc) to discuss this issue together (an internal NA4 group). 4. Data-Encryption: There is already one workgroup on this. DILIGENT may be interested in participate. * Action 4: CL will send more information about the group. * Action 5: PP will check FhG interest. 5. AMGA Metadata Catalog: BL described the status/goal of this service, pointing out that this is a good moment for DILIGENT to start using AMGA since it will be part of gLite from release 1.5 (http://project-arda-dev.web.cern.ch/project-arda-dev/metadata/).