1 / 11

SA3 Partner Status Report of TCD

SA3 Partner Status Report of TCD. Presenters: John Walsh, Eamonn Kenny Date: 22 nd May 2007 Location: PIC, Barcelona, ES. TCD Role. Main SA3 Role R-GMA T&C Porting & Porting Coordination. SA3 Partner Status Report of TCD. Testing and Certification. Testing and Certification.

dellis
Download Presentation

SA3 Partner Status Report of TCD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SA3 Partner Status Report of TCD Presenters: John Walsh, Eamonn Kenny Date: 22nd May 2007 Location: PIC, Barcelona, ES

  2. TCD Role • Main SA3 Role • R-GMA T&C • Porting & Porting Coordination

  3. SA3 Partner Status Report of TCD Testing and Certification

  4. Testing and Certification • 12 PM over 2 years • Since Nov’06 • Isolated testbed well established • Mostly Xen based • R-GMA servers (site MON and REG) non-virtualized • Talk about this on Thursday • T&C mostly concentrating on R-GMA • Established good rapport with R-GMA developers • Frequent face-to-face meetings • R-GMA developers provided extra tools for testing • Inspector • Comprehensive Unit tests for fixed bugs

  5. Bugs and Patches • R-GMA patches certified • #926 (with Maria Alandes), 13 dependencies • #1086, 0 dependencies • #1124, 5 dependencies • #1124, 4 dependencies • R-GMA bugs submitted • #23317, Inspector servlet with hard coded values • #23233, improved mechanism for detecting R-GMA uid • #23023, world writeable log file • YAIM config testsing tasks • Effect of moving from LCG RB+LB/CE to gLite equivs • Other bugs submitted • #23373, #23366,#23316

  6. Configuration Issues • R-GMA/TOMCAT/MySQL interaction • Tests show some potential issues with default configuration • TOMCAT Java memory management • JVM stack/heap/GC optimisations reduce OOM conditions • MySQL max_connections settings may to too low • Potential benefit in using connection pooling • Issues under investigation by R-GMA/TCD • Based T&C stress tests • Identified anomolies with external packages • Prevaler installed, not used • Mm-sql installed, not used • R-GMA JDBC different version from that used by other gLite componenets • Current JDBC may have memory leak & IPv6 problem

  7. SA3 Partner Status Report of TCD Porting Status

  8. Achievement Fixes and direct contributions to ETICS software: • Worked through the external dependencies to get newer versions into the repository • Changes to external dependencies: log4cxx, boost • Changes to org.glite: org.glite.security.voms • ETICS running on: SuSE 9.3, CentOS 4.4 (x86_64), Mac OS X (Panther/Tiger) • HTTPS proxy support seems to be now working. • Solved: RPM BuildArch translation issue, SPEC file issues under SuSE, ETICS bugs relating to database info, staging permissions issues • Created an alternative to webreactor in ETICS giving HTML reports which is now adopted • Got to 100% building in February for SL3 and CentOS

  9. Achievements • Condor auto-install under AIX, Mac OS X and Linux in preparation for NMI building • Automated hypergraph creation for interrogating dependencies quickly (proved useful) • Automated reporting of all builds (including synchronization of RPMs to a central server) • XML schema for stringing module building together (very useful for local or developer builds)

  10. Issues/Problems Large proportion of time is in dialogue Resolved Issues: • Default platform is no longer SLC3 • ETICS build system was too dependent on old gLite xml scripts • lack of access to ETICS database (given access 2007/05/14) Unresolved Issues: • better output in reports (submitted a Savannah bug report) • build system restructuring (monolithic build) • middleware re-working (comments by e-mail) • remote building issues (firewall issues) • slow integration of changes to databases (patching) • full monolithic build on Xen is too slow (--register will help)

  11. Next Steps Infrastructure changes: • Install NMI and possibly open Globus and Condor ports • Quattor configuration for co-existing Xen x86/x86_64 nodes Build Machine changes: • Condor DAG managed build submissions to combat Xen issues • Large number of edits to the ETICS database to sort MySQL, VOMS, boost, RGMA issues. Default overrides should help. • Register option needs to be tested • Patching prototype to be introduced if agreed • Multiple module building to override monolithic build

More Related