DILIGENT TCom

2 Oct 2006, 08:00 → 6 Oct 2006, 18:00 Europe/Zurich

Basel

Around 20 participants (mainly people involved in the technical activities). Activity: - Overall delay estimated to 2 months (4 months of which 2 will be recovered by the contingency plan). - Agenda for the 2nd review drafted. Release Alpha: - Currently 46 services available and compliant with the Diligent framework. Final deadline for all partners to complete the release candidate alpha developments is October 13. Then the build process will then start followed by the deployment testing activity up to October 27. DILIGENT infrastructure status: - Many DILIGENT services already deployed in the DILIGENT infrastructure "represented" by 81 running instances distributed on 32 hosting servers (at least from 4 sites). The latest status can be browsed here: http://dlib-services.isti.cnr.it/DIS/ - Most gLite services of the development, testing and pre-prod infrastructures are up and running gLite 3.0.0 DILIGENT in ETICS: - 16 subsystems and 115 components modeled in ETICS. Some parts still missing from FhG. About 30% correctly builds. Main problems linked to wrong configurations entered in ETICS (checkout, build commands, dependences). ETICS reports available at: http://grids16.eng.it/BuildReport/index.jsp - ETICS Training was given by CERN and ENG. The training session was very well received by the participants - feedback collected from partners and given to ETICS. - How the DILIGENT integration testing activity can be integrated in the current version of the system is still being analyzed and tested. - Currently only one person for each DILIGENT partner has access to ETICS. Access for all DILIGENT members promised for soon. Security Model: - It has been raised (again) that there is no definitive agreement on the security model to use (user or service owner certificates). However, a first implementation based on service's owner certificates will anyway be available for the Release Alpha. Content Management: - Exploitation of LFC is still unclear and limited effort is spent in trying to solve the blocking factors. - Need for the GFAL Java API has again been stressed. Currently Content Management is using the NA4 Java API developed in Catania. This API is not officially part of the distribution and is buggy (bug submitted to GGUS, reaction is slow). This requirement, between others, have been presented to EGEE and are included in the DILIGENT MoU. - A possible need for a meeting with EGEE LFC/GFAL experts have been raised.