Operations meeting

→ Europe/Zurich
28/R-015 (CERN)

28/R-015

CERN

15
Show room on map
Nick Thackray
Description
Phone: +41 22 767 7000 \"Grid Operations/Ian Bird\"

ACTION LIST

Weekly Operations' Meeting 2005-03-14

Agenda: http://agenda.cern.ch/fullAgenda.php?ida=a045858
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: Stephen Burke (RAL, UK), Alessandro Cavalli (INFN), Maria Dimou (CERN, Secretary), Sven Gabriel (FZK), John Gordon (part-time, RAL, UK), Holger Marten (FZK), Gilles Mathieu (IN2P3,FR), Gonzalo Merino (PIC, SWE), Ian Neilson (CERN), Piotr Nyczyk (CERN), Marcin Radecki (CE), Rolf Rumler (IN2P3,FR), Philippa Strange (RAL, UK), Nick Thackray (CERN, chair), Steve Traylen (RAL, UK), Min Tsai (CERN & Taiwan), Jules Wolfrat (SARA, NE). 
Apologies: 
Absences: There were reports but no participant from SEE (Clean Monday, public holiday in Greece) or Russia.

Comments on the notes of the last meeting:
The action list will now become a separate file that will be linked from the CIC web site as well.

CIC & ROC reports:

CIC-on-duty report (Alessandro from CNAF):
A full report is in the CIC-on-duty log, starting as [2005-03-14 10:42] - Alessandro Cavalli

ROC reports must be uploaded to this meeting's agenda 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 and from the 2005-02-28 meeting's agenda. 

Issues discussed in addition:
1. French participants asked what an RC can do if they need users' email addresses. The answer is to send email to Lcg.Registrar@cern.ch which will give out the information provided the request is properly justified according to the User Registration Requirements' document (section 5 on Site responsibilities & requirements).

2. NE: NIKHEF didn't upgrade part of their resources to LCG2 2_3_0 because of D0 request.

3. UK: Fedora sites never managed to make LCG2 2_3_0 install but they now try to go to LCG2 2_3_1 .

4. On the site escalation and banning issue with the occasion of Carleton and BNL and the SEE ROC reminder that the GDB is not the body for escalation of problems in the EGEE community, the result of email interactions during the week was that the GDB is not the right body. The OMC (Ian Bird) will authorise ite banning, when necessary. The ROC managers' meeting will probably discuss the issue on March 15th anyway and will report the outcome next time.

5. On the issue of repetitive BDII instabilities that Kostas reported last time, Laurence Field advised to install the BDII on a separate machine and also gave them a new version of the BDII that is even more perfomant for them to test.

6. The move from https://savannah.cern.ch/projects/lcg2sites/ to GGUS starts now, will last for 2 weeks and will be handled by IN2P3 and CERN. Existing tickets will be drained in the present system. This was announced with the following message:

From: egee-broadcast@cern.ch
As decided at the beginning of this year (COD-1 in Lyon and ESC-meeting inKarlsruhe), The CIC-on-duty Operations will soon stop
using Savannah and use GGUS for all the Ticket Submission stuff.
                                                                          
The idea was basically :
- GGUS provides  a special Helpdesk for CICs-on-duty
- The CIC portal provides the interface to view, create, modify tickets
                                                                          
This will allow the CIC-on-duty Staff to handle tickets and contact sites
using the same entry point.
                                                                          
We agreed to start using this mechanism on our IN2P3 on-duty week, i.e.
today.
- No more Savannah tickets will be created. Each new ticket will be a GGUSone.
- CIC-on-duty staff will have to deal with both Savannah and GGUS, until
we have drained all open tickets in Savannah.
                                                                          
ROC Helpdesks will be assigned GGUS tickets and will have to treat them,
just as they used to with Savannah.
                                                                          
After IN2P3, CERN is on-duty. The CERN team knows quite well what is goingon with this. This will give us 2 weeks to test, change,
                                                                          
and use the new interface, and then to formalize, describe and explain
what are the involved changes for CIC-on-duty operations.
                                                                          
We\'ll do our best to make this transition as soft as possible.
 

Security report (Ian Neilson):
- A lot of discussion in various mailing lists took place for several days on whether the russian site Protvino (IHEP.RU) has been hacked.

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

Action List now in http://cern.ch/dimou/lcg/gdaActions.html

Next meeting:

  • The next regular telephone meeting will take place on Monday March 21st 2005 from 14:00 to 16:00 in conference room 28-R-015.

Maria Dimou, IT/GD, Grid Infrastructure Services




 

Weekly Operations' Meeting Action List

 

 Status of 2005-05-09

NumberDescriptionAssigned To:Status
2004-12-06--1

Sites should accelerate migration away from RH7.3 (and other non-secure OSs), at least on the service nodes due to security considerations. Deadline: End of April 2005.

Progress:
Frederic: French sites will be done by the end of May. 
Gonzalo: 3 sites remains in SWE.

ROC mgrsOPEN
2005-02-07--4John Gordon volunteered, using some information circulated by Ian Bird, to define metrics on site performance. 
Progress:
Min working on this now.
NickOPEN
2005-02-14--5Merged with action 2005-02-14--4: Provide a page, probably hunging off the Regions' page) with a flag indicating whether a site had been down over a given period and foresee use of this info in the reporting template. Details in the action list of the 2005-02-28 meeting notes.Piotr & MinOPEN
2005-02-28--1

Sites to set the value of max_running_jobs to the number of available CPUs instead of 9999 for those cases when there is no limit. Progress will be monitored via the ROC managers' meeting. This is an ATLAS request. 
Progress:
Read the notes of the Feb.28th meeting for the reasons of this request. Value 9999 is set to zero. Nick will check with Simone Campana whether Atlas is happy.

On 2005-05-02 meeting Simone reported that no more 9999 value is present but far too mamy zeroes, which means no jobs are accepted in that site. Gonzalo this is the default Info provider value. He suggested obliging the site to put a value. Simone will discuss it with the customers and the deployers.

Simone to Oliver??OPEN
2005-03-14--1

Analyse the information submitted by the ROCs in the weekly reports over a number of weeks, to see what can be learnt from it.

Progress:
tailoring, filtering in the new form by Osman.

NickOPEN
2005-03-21--1Resolve conflict of interests between the ROCs which make RCs available for VO support and VOs which desire to black/white list sites based on the Site Functional Test (SFT) results. 
Progress:
Sven Hermann reminded the ROC managers list this should be discussed in their meeting of 2005-05-03.
ROC mgrs meeting & EIS-experiment meetings.OPEN
2005-03-21--2Document in the Operations Manual that, after initial contact with the site and the ROC, escalation will go to the ROC only (and no more to the site) by the CIC-on-duty.PiotrOPEN
2005-04-11--1Lack of possibility for CICs to run the cron job that produces that Functional Site Reports (FST) daily is a problem. 
Progress:
Now Frederic,Piotr and Judit have permissions for cvs updates, the cron changes automatically to incorporate recent changes committed into cvs.
Piotr & CICsDONE Close at next meeting
2005-05-02--1Change http://egee-docs.web.cern.ch/egee-docs/list.php?dir=.\operational_tools\& to point to https://cic.in2p3.fr/index.php?id=roc&roc_page=1NickOPEN
2005-05-02--2CMS requires a normalisation of OS used by the sites. Define agreed list of names and publish it with the next Release Notes.MarkusOPEN
2005-05-02--3Clarify the policy concerning VO data lost on a SE.NickOPEN
2005-05-02--4Make SFT easily configurable for VOs. Obtain critical SFTs per VO.Piotr & EISOPEN
2005-05-09--1Discuss site suspension and re-integration procedures.Bologna LCG Workshop participants 2005-5-23OPEN

 

Maria Dimou, IT/GD, Grid Infrastructure Services
 


There are minutes attached to this event. Show them.