Akos Frohner (minutes) Peter Kunszt Ricardo Rocha Krzysztof Nienartowicz Gabor Gombas Kalman Kovari Paolo Badino Daniel Rodrigues Erwin Laure Actions: Slides for Frédéric: Péter prepares them and bounces around for review. BS meeting: Krzys and Ákos would go there next week. Slides for 7th of April: Krzys and Ákos, after the BS meeting with a better understanding of the requirements. In the course of discussion on what shall we adverstise on Fireman: - performance? we can promise to implement a non-ws interface, if it is really needed. - metadata support: the interface is negotiated in the EGEE PTF with the experiments (ARDA group, to be precise) - web-services interface, with change management (EGEE PTF) has the advantage of support to various client languages: C (also a simplified C API), C++, Java, Perl and JavaScript (for web clients) - support? EGEE provides the support for Fireman, but what would happen, when EGEE finishes? - two implementations: MySQL and Oracle for laptop and production usage (two extreems) - POOL integration (ongoing effort) - distribution (planned, with a proof-of-concept prototype) Experiment requirements (as we understood them so far): Alice: intends to use AliEn LHCb: open to suggestions, but first testing LFC CMS and ATLAS: emphasis on local catalogs, since they would provide a higher level functionality with their own services We should understand better the dataset use cases! (-> Ákos should talk to Peter Elmer/CMS) Dataset uses cases: 1. bulk upload of files for datasets [Ákos: we are covered with the current Fireman] 2. transfer of datasets this needs interaction with FTS/FPS/DS, which depends on what catalog is used actually 3. access to dataset: look up dataset on a central service, which points to a local file catalog, describing the details of the datasets Q: what is ready, what could we offer from gLite? a) experiment's dataset service b) metadata catalog as dataset service c) Fireman as dataset service We should clarify the interactions (updates from local catalogs and queries bouncing on the dataset catalog) and fix them in some interfaces.