Deployment team

Tuesday 11 Dec 2007, 11:00 → 12:15 Europe/Zurich

EVO - GridPP Deployment team meeting

Jeremy Coles

- This is the weekly DTEAM meeting - The intention is to run the meeting in EVO: http://evo.caltech.edu/evoGate/. Join the meeting in the GridPP Community area The phone bridge number is +41 22 76 71400,. Th phone bridge ID is 12454 with code: 4880.

Minutes dteam-07-12-11.txt

11:00 → 11:20 Experiment problems/issues

Review of weekly issues by experiment/VO - LHCb - CMS -- http://indico.cern.ch/conferenceDisplay.py?confId=22161 - ATLAS - Other - Sites CPU -- LT2: RHUL; QMUL; UCL-Central -- NorthGrid: Lancaster -- Scotgrid: Glasgow; ECDF -- SouthGrid: Cambridge; Oxford; RAL-PPD - Sites CPU accounting: -- EFDA-JET -- Bristol (early November) -- Oxford (early December) - Storage availability -- http://www.gridpp.ac.uk/wiki/GridPP_storage_available_monitoring

11:20 → 11:35 ROC update

ROC manager update ************************* The meeting was this morning - http://indico.cern.ch/conferenceDisplay.py?confId=23751 Ops meeting *************** - Latest PPS release gLite 3.1.0 PPS Udate 11 is about to be released to PPS It contains, together with the usual bug fixes, the new VOBOX service for SL4 (32 bit) glite-yaim-core has been released, all the metapackages have been updated. - gLite 3.1 Update 07 included patch #1389, an update to GFAL/lcg_util. A serious problem has been found with this patch, whereby lcg-cr segfaults with a classic SE endpoint - It is proposed to stop using dteam in SAM monitoring - The CERN default version of the AFS UI will be changed from gLite 3.0 to gLite 3.1. In practical terms this means that the 'current' AFS UI link will not point to the latest 3.0 version anymore, but to the latest 3.1 version. The change will happen this Wednesday, 12 Dec, 2007 10:00 CET (09:00 UTC) Ticket status *************** - See attachment

more information 071210_report.html

11:35 → 11:45 Areas that DTEAM could benefit from more Tier-1 input

- Discussion on several focus items coming from the Tier-1 review in which the reviewers indicated .... - (will be removed) - > 3.11 There is too much emphasis on internal "firefighting" of issues > that do not address the high-level user requirements. The Tier-1 > management team (AS, JG and NG) should address this together with the > Production Manager (JC). (Point-2.5) > > 3.13 The Tier-1 and the Production Manager should investigate ways to > strengthen the integration of the Tier-1 with the wider deployment > team. Greater involvement is required at this level. A dedicated > meeting is suggested. This needs to be addressed as a first step > towards a Tier-1 Service Delivery Plan. (Points-2.6 and 2.7) > > 3.14 The UK deployment team needs to be informed of the Tier-1 > deployment requirements. (Point-2.6) > > 3.17 Improved procedures for documenting and replicating the above > services as part of a resilient Grid should be established via the > Production Manager and together with the deployment team. (Point-2.7)"

11:45 → 11:55 Feedback from the ATLAS jamboree

- http://indico.cern.ch/conferenceDisplay.py?confId=23620 - ATLAS plans - Requirements on Tier-2s - Points to note

11:55 → 12:05 Actions review

12:05 → 12:10 AOB

- Testing Nagios central publishing T2 volunteer needed