Choose timezone
Your profile timezone:
Operations meeting
→
Europe/Zurich
CERN
CERN
Description
Phone: +41 22 767 7000 \"Grid Operations/Ian Bird\"
Weekly Operations' Meeting 2005-04-11
Agenda & Action List: http://agenda.cern.ch/fullAgenda.php?ida=a045862
Operations' Manual: http://lcgdeploy.cvs.cern.ch/cgi-bin/lcgdeploy.cgi/lcg-docs/EGEE-CIC-Operational-Manual/opMan.pdf
CA rpm instructions: http://cern.ch/grid-deployment/lcg2CAlist.html and https://cic.in2p3.fr/index.php?id=rc&subid=rc_config
Template for weekly report submission by the ROC: http://cern.ch/egee-docs/list.php?dir=.\operational_tools\&
Participants:
Asia Pac.: Min Tsai
CE: Marcin Radecki
CERN: Maria Dimou (Secretary), Ian Neilson, Piotr Nyczyk, Markus Schulz, Nick Thackray (chair)
CH/DE: Sven Hermann
FR: Helene Cordier, Pierre Girard, Gilles Mathieu, Rolf Rumler, Frederic Schaer
IT: Alessandro Cavalli, Paolo Veronesi
NE: Per Öster, Jules Wolfrat
SEE: Kostas Koumantaros, Ognjen Prnjat
SWE: Gonzalo Merino
Russia: Alexander Kryukov (RU, part-time; the telephone contact with Alexander was lost early in the meeting)
UK/IR: Jeremy Coles, Philippa Strange, Steve Traylen
Apologies:
Absences:
Comments on the notes of the last meeting:
This was not discussed. Maria updated some links that were pointing to older meetings (Nick was taking notes on Maria's previous meeting's template).
CIC & ROC reports:
Exiting CIC-on-duty (IT):
A full report is in the CIC-on-duty log, starting as [2005-04-11 13:36] - Alessandro Cavalli
ROC reports must be uploaded to this meeting's agenda as "More Information" by the CIC-on-duty and the ROC managers themselves by 11am CET. The report template, is linked from the ROC views of the CIC web site. NB! New template!!
Issues discussed in addition:
FR:
Frederic reported that the lack of possibility for CICs to run the cron job that produces that Functional Site Reports (FST) daily is a problem. Piotr, who owns the only authorised login to run the jobs will discuss with the CICs a solution to this.
The remaining 6 french sites to upgrade to LCG2 2_4_0 will be done next week.
IT:
Sites which didn't install LCG2 Rel. 2_3_1 will go to 2_4_0 directly and they will move to SL3 OS or compatible. Upgrades will start next week.
UK:
Not all sites will upgrade in time, i.e. until the end of April. Queen Mary University loses the people who would have done the upgrade. They should be removed from the LCG sites because the site will be unattended.
An RB used by LHCb and BaBar is not working. Users are informed.
CH/DE:
On new LCG2 release deployment:
Sven expressed concerns whether upgrade to the new release can complete for all sites in the region in 3 weeks. He claimed that 4-5 weeks are more realistic. Markus replied that, if we accept, officially, a 6-week delay people will drag-on and then, they won't upgrade at all, waiting for the next release. Ian reminded that any such flexibility shouldn't apply to security updates' releases which must be installed rapidly and maybe at short notice. The process of excuding the sites in the functional tests should be the same for normal releases and security ones. Ognjen said release installation deadline set to 3 weeks should be approved by the ROC managers. Markus reminded that this delay was agreed at the last LCG Workshop at CERN in November 2004 and, if needed, it should be re-discussed at the next Operations' Workshop in Bologna.
On technical issues of service components:
WNs need outbound connectivity in order to contact the registry. Inbound connectivity is not needed. Technical questions on R-GMA configuration can be sent to Steve Traylen.
It is not a good idea to mix 2_4_0 service nodes with 2_3_1 WNs due to R-GMA dependencies.
On hand-over between "Support On Duty" (SOD) centres:
Some details on how to do that are not quite set as a standard procedure, the issue should be taken offline within the mailing list egee-ggus-feedback@cern.ch
CE:
Service nodes and worker nodes run on 64-bit processors. They will contact Andreas Unterkirche about progress on building this release's RPMs for this architecture.
SWE:
Can yaim be used for re-configuration as well as initial installation? Markus said 'yes' and if a bug is found, please put it in savannah and copy Oliver.Keeble@cern.ch
Write to egee-ggus-feedback@cern.ch for remedy searches that help selecting sites directly.
SEE:
SFTs are critical. BDII update wil not be triggered automatically from the SFTs but there soon will be a web page per VO, where the VO will choose which tests they consider important. They can, then, if they wish, use this result to configure the BDII.
Asia:
Taiwan and Singapore are still in RH7.3
NB! All CICs, please, re-visit the on-duty rotation agenda.
Security report (Ian Neilson):
- CA rpm update is not always related to security. Upgrade delay will be dictated by the OMC (Operations Management Centre).
Next CIC-on-duty:
- The CIC-on-duty this week is IN2P3.
- The actual work is be done by the ROCs and the follow-up by the CICs. The CIC-on-duty just does the monitoring.
- The ROC managers should remember that when a problem at a site is solved the site needs to go through a period of quarantine before joining production again. This is mentioned in the Operations' Manual.
- The CIC site (requires personal certificate loaded) is http://cic.in2p3.fr .
- Link to the daily Site Status reports.
- Savannah should be used for the Tasks' hand-over and follow-up. The Operations' Manual should be the basis.
- When the CICs report also as ROCs, they should do this in separate reports.
- Sites' status of updates can be checked in the daily reports e.g. http://cern.ch/lcg-testzone-reports/cgi-bin/lastreport.cgi
A.O.B.
- CIC portal unavailable tomorrow and to be upgraded next week.
- Monitoring should be based on functional aliases indicating the service a machine offers and not on primary hostnames.
Next meeting:
- The next regular telephone meeting will take place on Monday April 25th 2005 from 14:00 to 16:00 in conference room 28-R-015. EGEE Conference in Athens next week, no meeting.
Maria Dimou, IT/GD, Grid Infrastructure Services
There are minutes attached to this event.
Show them.