EGEE'06

26 Sept 2006, 08:00 → 30 Sept 2006, 18:00 Europe/Zurich

Conference website

Tuesday 26 September

08:00 → 08:20 DILIGENT participation at EGEE'06

Slides

• DILIGENT_at_EGEE06.pdf
• DILIGENT_at_EGEE06.pdf
• DILIGENT_at_EGEE06.ppt
• DILIGENT_at_EGEE06.ppt

DILIGENT DEMOS AND POSTER SESSION Comments from Veronica (ESA) The project had a very positive feedback: we received a lot of interested visitors and here follows a resume on the most important comments and FAQs Vangelis and I received during that session. 1) Most of the visitors know Diligent or anyway they heard about it. 2) People want to be updated on the project current status as they want to use it: they complain about the lack of targeted and clear information from the website. Most of the visitors who already knew Diligent think to it as of a big "distributed DB over a grid infrastructure". They were surprised about the ability to run computationally demanding applications (e.g. EO apllications) to process data. They didn't mind about the concept of digital library: in my own opinion a clear and simple overview on the general data anagement services a DLMS may offer should be well advertised on the web site and it should also be better explained what a digital library is (maybe through examples). End-user communities applications have then to be more advertised. Both the concept of report generation service and course management service have been seen as general services feasible to apply to any type of content. 3) People want to use Diligent. They look at Diligent as a powerful mean to have their huge amount of content easily available via web. They'd like to provide us with their content. - It is not clear to them wether Diligent is a open infrastructure or not. People want to know wether they can provide us with their content and wether their content would be simply indexed residing on current sites or even moved to other sites. As an example take an egee sites provider whose data are already on egee SEs. - Visitors' content consists mainly of textual documents, images, streaming video, slides. - People would like to know exactly what has to be done and which is the amount of work required to make their content accessible to Diligent in terms of metadata management. - How are metadata managed in Diligent? Where are metadata information stored? How are metadata files linked to content files they refer to? 4) People asked for code availability 5) People asked for downloading the posters: they should be easily accessible from the project website The visitors we received come from academic institutions, research centres, international organisations and may be directly involved in egee activities. Finally, a section on this event together with FAQs and answers should be advertised asap on the web site, before the review. If you do agree, comments and answers on this resume will be surely welcome and useful to everyone: the project should shows a unique and common line to face such comments.

Thursday 28 September

08:00 → 09:00 EELA meeting

**20k euros** *CERN will provide to EELA access to shared CERN production resources =>action: Florida to coordinate admin/financial aspects with CIEMAT/Raquel. update: Florida re-sent to Jesus supporting docs, still no answer from CIEMAT re financial accounting =>action: Frederic to make the resources available to EELA as soon as possible, preferably in time for the Wisdom data challenge. update: Frederic has initiated the process to make the resources available to EELA **Operations** *EELA will continue building their own ROC; they plan to have 24h support to sites, profiting from the geographical location of the different sites, and from Alexandre Duarte being at CERN. *Alexandre will be involved in the CERN ROC team to learn all tools and procedures, and will manage the SAM server for EELA. SAM will be hosted by CIEMAT. *EELA will send a monthly report with a summary of the progress in this area and the points to work together after the March07 review. This will be the way to agree the next steps. **Review** *Proposal: 12-14 March (EELA, EUMed, EUChina reviews) 15-16 March concertation event among regional extension projects + EGEE *Review preparation needed, as most LA partners are new to the EC review *Anna & Dita (EGEE PO) are helping Raquel & Felix with admin/financial side of things, plus review pointers =>action: Diego/Roberto to propose demo scenarios **gLite/OurGrid interoperability** On hold until Brazilian funding is confirmed. If funded, start date is Jan07. =>action: Roberto to send justification (technological, regional, political, etc) of this interoperability work.

09:00 → 10:00 EUChina Interoperability gLite-GOS

These are the notes I took on-line at the EUChinaGrid session: Security -------- Certificate from CNIC-CAS (part of IGTF) Proxy included in the token Users accessing CNGrid will use a unique proxy Attributes will not be considered at the time being Information ----------- CNGrid has a montoring system that collects info at the sites Is it possible to use that information to populate the ISM? And bdII? Deploy a single gateway tocollect the info form all sites? The original questions in slide at the panel were: Security -------- Does a GOS user have a certificate/proxy? Are the CA’s mutually trusting each other? How do we move attributes from the GOS tokens to VOMS FQAN? How do we get a token starting from a certificate + VOMS FQAN? Information ----------- How do we publish the status of CNGrid resources to the bdII? Individually or as a whole? Does CNGrid need to get the EGEE resource status into an Info Sys? Job management -------------- Is it possible to consider the whole CNGrid as a gLiteCE/CREAM? Do we have all the bricks to build the BLAH plug-ins for CNGrid? Can we install the gLite client code on the WN’s? Can GOS consider the gLite WMS as a gateway to EGEE? Do GOS need client code to be installed on EGEE WN’s? Data Management --------------- Is it possible to build an SRM interface in front of the GOS file system? Can the GOS architecture accommodate a Storage Element? For what concerns a meeting on the interoperability I'll try to understand what the possibilities are. Claudio