JRA1 Middleware Re-engineering Status Report Francesco Giacomini JRA1 Activity Leader INFN EGEE-III First Review, 24-25 June, 2009 1

Activity Overview Country Total PM planned at M24 Total FTE CERN 78 3.3 Czech Republic 48 2.0 Finland Italy 256 10.7 Netherlands 35 1.5 Switzerland 36 UK 30 1.3 Total 531 22.1

Effort spent at M8 Country PM planned PM consumed Deviation CERN 26 36.5 +40.3% Czech Republic 16 16.3 +1.8% Finland 18.9 +18.0% Italy 85.3 90.2 +5.7% Netherlands 11.7 15.1 +29.4% Switzerland 12 14.5 +21.0% UK 10 33.6 +235.8% Total 177.0 225 +27.1% Based on information included in the Country Reports Some overspending by some partners All understood No impact is expected for their contribution during the rest of the project

Tasks TJRA1.1 Middleware support maintain and gradually improve the reliability, performance, usability, and manageability of the existing services Support via Savannah and GGUS (best-effort) TJRA1.2 Research & development and standardisation development of components needed for an effective usage of the production resources and [...] adoption of consolidated international standards Main development is a coherent Authorization Framework TJRA1.3 Activity Management Includes Security Architect

Components Security VOMS and VOMSAdmin Proxy and attribute certificate renewal Shibboleth interoperability LCAS, LCMAPS gLExec Delegation framework CGSI_gSOAP Gsoap-plugin Trustmanager, Util-Java GridSite Authorization Service Information, Monitoring GLUE Schema, BDII R-GMA Job Management CREAM, CEMon BLAH WMS Logging and Bookkeping Data Management DPM GFAL LFC FTS lcg_utils EDS, Hydra

Major achievements Middleware Support Releases for all the services/components have been delivered to certification and production Bug fixes Improvements in terms of reliability, performance, usability, and manageability Minor functional enhancements Development The certification of the new Authorisation service has started Standardisation The GLUE Schema v. 2 has become an OGF standard SRM v. 2.2 adopted by the gLite Storage Element (DPM) JSDL support by the gLite meta-scheduler (WMS) BES/JSDL adoption under discussion for the gLite CE (CREAM) Co-chairing the OGF PGI WG SAML support by VOMS

Workplan Integrated in Savannah Links to other tasks, patches, bugs

Configuration Management Managed with ETICS Platforms, dependencies, node types, etc.

YUM repository Automatically generated YUM repositories are extensively used for testing

Automatic testing: VOMS System testing, library testing and regression testing Requires deployment of a functional VOMS server instance, including a MySQL database Run remotely on ETICS after a build Results integrated in the build report

Portability to multiple platforms Slow progress Limiting factors Lower priority than other needs Lack of effort dedicated to integration activity Getting better WN releases available on SL4, SL5 Debian 4 in certification UI releases available on SL4 and SL5 gLite 3.2 integrated builds address at the same time Scientific Linux (CERN) 4 and 5, Debian 4 and 5, MacOS X, both 32 and 64 bit architectures (where applicable) Success varies from ??% to 100% Nightly builds are available through ETICS

IPv6 Collaboration with SA2 They ran the IPv6 static checker as an ETICS plugin and submitted 110 bugs 75 for JRA1 components Bugs are being fixed Important but not urgent task 42 bugs fixed in CVS or already closed, 33 still to be addressed Final testing to be done by SA2 on their IPv6 testbed Some services are IPv6 ready Production LFC, DPM Prototype BDII

Metrics

Metrics Number of bugs (development, release preparation, production) vs time

All-Hands Meetings An All-Hands meeting every six months 5-7 November 2008, Prague 6-8 May 2009, Nicosia Together with SA3 One day in common, one day Activity-specific

Goals for Y2 Prepare for the transition EGEE → EGI The software process for the Unified Middleware Distribution is based on distributed teams, responsible for all aspects of a software product Development, testing, certification, release, support, ... Consolidation of the software Multi-platform support Review of error messages and logging Documentation, especially of interfaces Appropriate copyright and license attributions Minimization of dependencies Provision of a gLite SDK Organization Moving to a more distributed model From Clusters of Competence to Product teams Need to adapt the existing process Establishment of a gLite Consortium to provide a long- term sustainable roadmap for the gLite software to meet the needs of its diverse user community beyond the EGEE series of projects

Summary All Activity tasks proceed according to the plan Deviations in effort consumption are not worrying Collaboration with SA3 and the ETICS team allows to overcome difficulties The software process and management procedures are increasingly based on the available tools Mainly ETICS and Savannah Transition to EGI requires changes both in organization and focus of technical activity