Deployment team & sites

Tuesday 1 Feb 2011, 11:00 → 12:16 Europe/London

EVO - GridPP Deployment team & sites meeting

Jeremy Coles

- This is the biweekly DTEAM & sites 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 +44 (0)161 306 6802 (CERN number +41 22 76 71400). The phone bridge ID is 77907 with code: 4880. - Apologies: Raja, Mingchao, Graeme

Minutes minutes-20110201.txt

11:00 → 11:20 Experiment problems/issues

Review of weekly issues by experiment/VO - LHCb -- Glasgow's transfer issues resolved: http://tinyurl.com/6gbcq54. See https://gus.fzk.de/ws/ticket_info.php?ticket=66203. "...lost network tuning on most of our workernodes, during a rolling rebuild." - CMS - ATLAS -- http://pprc.qmul.ac.uk/~lloyd/gridpp/hammercloud.html - Other -- T2K - Gustav appreciates the support received. - Experiment blacklisted sites - Experiment known events affecting job slot requirements - Site performance issues

11:20 → 11:35 Meetings & updates

- ROD team status (any points to raise to sites or issues to follow up?) - Tier-1 update Operational security -- Checking results at https://pakiti.egi.eu - LHC update "CERN's Machine Advisory Committee met over the weekend and presented its conclusions to management this afternoon. I'm pleased to report that they echo those reached during the annual Chamonix workshop that was held last week, making management's choices for the upcoming LHC run simple. The main decisions we have taken are that the LHC will run through 2012 before a long shutdown, we'll keep the energy at 3.5 TeV during 2011, and we'll work hard to increase the luminosity steadily." See the bulletin here: http://press.web.cern.ch/press/PressReleases/Releases2011/PR01.11E.html. Impacts on computing resources/pledges now need to be considered. Any immediate comments from the meeting here? GS yesterday mentioned a possible "resource problem for ATLAS (especially if we run at a higher trigger), so making sure all pledges are met and delivered is very important. Because of this we'll have less and less copies of data around the grid, so improving T2 reliability and availability becomes more important for delivering a reliable (integrated) resource to the experiments." - The next GDB is on Wednesday February 9th. The agenda is here: http://indico.cern.ch/conferenceDisplay.py?confId=106641. ARGUS and MUPJs are back on the agenda; information publishing (such as the VO shares); an update on EGI/EMI and particularly the middleware. Pete Gronbech is the Tier-2 rep this month.

11:35 → 11:45 Publishing VO shares

Ref: Email to TB-SUPPORT Friday 28th@15:00. You may be aware that the WLCG Management Board is currently validating information being published in gstat (for GridPP http://gstat-prod.cern.ch/gstat/summary/GRID/GRIDPP/). At the moment very few UK sites publish VO shares but we are now encouraged to do this (our ticket is https://gus.fzk.de/ws/ticket_info.php?ticket=66564 and for those who feel this is not necessary see a relevant discussion here https://gus.fzk.de/ws/ticket_info.php?ticket=66469). These shares are NOT used for scheduling, they are purely for project management and oversight (i.e. to see what is available to a VO). Some of us discussed the UK figures in the deployment meeting on Tuesday but we need to recheck details in the GridPP (Steve Lloyd) allocation spreadsheet before confirming the values we would expect to be published. If you happen to know already for your site please go ahead and publish now. Sites that are explicitly mentioned in the ticket as needing to do this are: EFDA-JET UKI-LT2-Brunel UKI-LT2-IC-HEP UKI-LT2-QMUL UKI-LT2-UCL-HEP UKI-NORTHGRID-LANCS-HEP UKI-NORTHGRID-LIV-HEP UKI-SCOTGRID-DURHAM UKI-SCOTGRID-ECDF UKI-SCOTGRID-GLASGOW UKI-SOUTHGRID-BHAM-HEP UKI-SOUTHGRID-BRIS-HEP UKI-SOUTHGRID-CAM-HEP UKI-SOUTHGRID-OX-HEP UKI-SOUTHGRID-RALPP RAL-LCG2 Publishing example: for RHUL the site-info.def entry: CE_CAPABILITY="CPUScalingReferenceSI00=1975 Share=atlas:97 Share=cms:1 Share=lhcb:1 Share=others:1" results in this in the information system: RHUL GlueCECapability Share=atlas:97 GlueCECapability Share=cms:1 GlueCECapability Share=lhcb:1 GlueCECapability Share=others:1

more information VO-shares.gif

11:45 → 11:50 WLCG Tier-2 availability, accounting and misc results

11:50 → 12:00 EMI release 1.0

- Current plans - Site feedback on proposals -- EMI 1 release is expected this spring -- It is NOT guaranteed to be an upgrade to all node types. Reinstallation may be necessary. This is due to changes in underlying repositories (eg a different Globus distribution). Details from Stuart: "Future plans: EMI 1.0 (due 30 April 2011) will bring some major changes, with impact onto SR process and EA sites: Use of a single repository for all packages (no more multiple gLite repositaries) Standard repository structure (base, upgrades and security) Use of EPEL for external dependencies (Dropping Dag reposites) Use of Globus from EPEL instead of VDT Change of installation root (/usr instead of /opt/XXX/, all configs in /etc) Note that there is no direct upgrade path from packages using Dag's repo to EPEL repo. (Implies that it'll be a case for a reinstall, rather than upgrade). gLite 3.2 and Arc 0.8 will be supported until EMI 2.0 (due 30th April 2012)." -- Difficult to understand the impact until we know which nodes will be affected, but is there any initial feedback? Details are in slides here: https://www.egi.eu/indico/contributionDisplay.py?sessionId=4&contribId=36&confId=153

12:00 → 12:05 AOB

- RAL currently publishes itself (via the BDII) as belonging to the grids WLCG, GRIDPP and EGEE. Should this list be changed to include, say, EGI or NGI?