LCG Service Coordination Meeting
Internal meeting for host laboratory LCG service providers focussing on issues on a timescale of ~1 week to ~1 month.
Mailing list: lcg-service-coordination-meeting@cern.ch
-
-
10:00
→
10:20
Outstanding Issues & Actions 20m
-
Reinstallation of service nodes - target end 2006Basically just the CEs (in progress) and VOMS (plan being prepared) that are left.
-
prod-lfc-atlas-central.cern.ch - status and plansThe so called "central" lfc is prod-lfc-atlas-central.cern.ch. It is not used by the ATLAS DDM but unfortunately has a legacy role for the users.
Q: when can we shut it down? 31st April 2007?
-
CASTOR interventions - update on scope & scheduleThis should cover not only the Western Digital interventions, but also the various - many other things coming along:
- Pending moves to new h/w of the various CASTOR components
- Upgrade of CASTOR s/w components
- etc.
All these things have to be scheduled in / around the expeirments' FDR preparations and on-going productions
-
Cleaning of databases prior to multi-VO testsOn several occasions, the database behind various services have needed to be "cleaned" to prevent performance degradation. This has applied to CASTOR DBs, FTS, dCache etc. Have all the necessary cleaning operations been performed at CERN and outside sites ready for the multi-VO throughput tests starting March 26th? Should these operations be performed regularly? Automatically?
-
Service Resilience to "glitches"How robust are the current services to short-term "glitches" (longer term outtages is a separate but needed discussion...)
Examples include:
- Power glitch - all machines protected up to 10' (the definition of a "glitch" (A fault or defect in a system or machine)?)
- Rolling upgrade / loss of contact to DB backend
- OS patch / upgrade
- m/w patch / upgrade
More major interruptions - such as loss of network switch / non-rolling DB upgrade - need also to be considered and where possible protected against.
H/W upgrades / moves -> rolling where possible?
-
Oracle Critical Patch UpdateCritical Patch Updates - see Release Schedule
Starting 2005, Critical Patch Updates are the primary means of releasing security fixes for Oracle products. They are released on the Tuesday closest to the 15th day of January, April, July and October. The next four dates are:
- 17 April 2007
- 17 July 2007
- (16 October 2007)
- 15 January 2008
-
Other changes in the pipeline
-
Status of Service Intervention Assistant
-
-
10:20
→
10:40
LCG Service Review 20m
-
<a href="https://twiki.cern.ch/twiki/bin/view/LCG/LcgScmStatusDeploy">Certification / Pre-production</a>Highlights:
- Patch #1078 (GFAL 1.5.0 and lcg_utils 1.9.0) had to be withdrawn from PPS as it was found that lcg-del does not work on a classic SE. A follow up patch is already available (#1101 GFAL 1.9.0-2/lcg_utils 1.5.1-1 already in the PPS).
- The SL4 natively compiled WN is now being deployed in the PPS.
Breaking news: There is a problem with configuration of the new WN which will prevent it being released to production, although it will be tested in the PPS.Speakers: Nick Thackray, Oliver Keeble -
<a href="https://twiki.cern.ch/twiki/bin/view/LCG/LcgScmStatusMLR">Monitoring, Logging & Reporting</a>Speakers: Ian Neilson, James Casey
-
Core Grid ServicesSpeakers: Gavin McCance, Jan van Eldik, Thorsten Kleinwort, Ulrich Schwickerath
-
Fabric & Infrastructure ServicesSpeakers: Maria Dimou, Maria Girone, Remi Mollon
-
Experiment Issueswiki page
The primary purpose of this item is to bring up any (hopefully rare) issues that are in danger of becoming "hot" if not given attention.
By definition, this must be used sparingly (i.e. not for every single problem seen by an experiment) and experience has shown that these issues should be raised in advance, e.g. the day before (or even earlier if possible...)
Speaker: EIS Team
-
-
10:40
→
10:45
Any Other Business 5m
-
WLCG RAC Weekly Report 15m
-
-
10:00
→
10:20