Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    Operations meeting

    → Europe/Zurich
    CERN

    CERN
    Ian Bird
    Description
    Phone: +41 22 767 7000 \"Grid Operations/Ian Bird\"
    Hide

    Weekly Operations' Meeting 2005-02-07

    Agenda: http://agenda.cern.ch/fullAgenda.php?ida=a045853
    Operations' Manual: http://lcgdeploy.cvs.cern.ch/cgi-bin/lcgdeploy.cgi/lcg-docs/EGEE-CIC-Operational-Manual/opMan.pdf

    CIC & ROC reports:

    From this meeting onwards reports are submitted by the CIC-on-duty and the ROCs according to this template:

    Weekly Operations Status Report: [ROC/Tier 1 name]
Reporting Period:                [dd/mm/yy] to [dd/mm/yy]
                                                                                
Number of sites in region:       [Total number of sites in the region, on the day of the report]
ROC/Tier 1 Manager:              [Enter the name of the ROC/Tier 1 manager(s)]
                                                                                
Number of "bad" sites at START of week: [How many bad sites were there at the start of the week]
Names of "bad" sites at START of week:  [Name the bad sites at the start of the
week]
Number of "bad" sites at END of week:   [How many bad sites were there at the end of the week]
Names of "bad" sites at END of week:    [Name the bad sites at the end of the week]
Which sites were "bad" all week?        [List any sites which were marked as bad all week long]
                                                                                                                                                            
Major operational issues encountered during the week:
[Describe the main problems encountered during the week.  If none, say "none"]
  
Upgrade to LCG-2 2.3.0
Have all sites upgraded to LCG-2 2.3.0? ["Yes" or "No"]
Which sites still need to upgrade?      [List the sites]
When will the upgrade be completed?     [Estimated date by when the upgrade will be complete at each site]
 
Upgrade to Scientific Linux 3 (or equivalent)
By when will all service nodes in region be upgraded? [Best estimate of the date]
By when will the WNs in the region be upgraded?       [Best estimate of the date]
 
Other Comments
[Enter other comments, clarifications, etc. here]
 
Points to raise at the Operations Meeting
[If you wish to raise any points for discussion at the weekly operations meeting, please put them here.]

    Reports should be sent to the project-egee-roc-managers@cern.ch list by 11am CET and are linked from the meeting agenda. CERN submitted no report due to preparation of the EGEE review. Russia submitted no report and nobody joined the meeting.

    Issues discussed in addition:
    - GOC db read-only replica available in Taiwan. Information:
    Server: goc.grid.sincia.edu.tw
    Access method: via mysql port 3306
    Access accounts: same as original gocdb

    - Some italian sites will only be known to GridIT and will not properly register in GOC db. Maria Dimou expressed worries about security incident follow-up, when necessary, in such cases.

    - Queen Mary University in London can't upgrade to LCG2 2_3_0 because they run on the Fedora OS and the installation can't complete.

    -The ROCs have to contact their sites in case the number of CPUs they have or the OS version they run is wrong in GOC db.

    - The Poznan site in Poland disappeared from the GOC db because the "Status" field value for its CE is set to 'test' and must be changed to 'lcg2'.


     

    Security report (Ian Neilson):
    - There was a problem between the Royal Holloway site and DESY.
    - As RedHat7 will soon be unsupported, sites are urged to move to SL3 for service nodes. The WNs can run the OS that the applications require.

    Next CIC-on-duty:

    • The CIC-on-duty this week is INFN.
    • 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:

    (*** ACTION 2004-11-29--1 ***)Vincent Breton to check with the other application managers the "Migration to SLC3 plan" of non-HEP VOs. OPEN

    (*** ACTION 2004-11-29--5 ***) Steve Traylen, with help from Laurence Field to document on the Wiki page for the sites on how to block users, when necessary. OPEN

    (*** ACTION 2004-12-06--1 ***) Sites should accelerate migration to SLC3, at least on the service nodes due to security considerations. OPEN

    (*** ACTION 2004-12-13--1 ***) Escalation procedures in the Operations' Manual should clarify that sites running outdated LCG2 versions or don't respond to CIC-on-duty action prompt will be disclosed in this meeting. OPEN

    (*** ACTION 2004-12-13--2 ***) Savannah accounts were created for all the ROCs. New users had to activate these accounts but as some failed to do it in time, their accounts have now expired. Now A. Kryukov has to re-create the Russian ROC account(s). OPEN

    (*** ACTION 2004-12-13--4 ***) Nick Thackray to send email to the 3 relevant ROCs about Helene Cordier's reminder to UK, IT and RU to submit their test suites as agreed in The Hague. OPEN

    (*** ACTION 2005-01-03--1 ***) Grid Infrastructure Support Section to give generic (functional) DNS aliases to important service nodes, ensuring transparent service changes. OPEN

    (*** ACTION 2005-01-10--1 ***) Frederic Schaer will enter a bug in savannah, project=lcgoperation, requesting a proxy at site level protecting from asynchronous updates of the CA list on various nodes at a site (RB, WNs etc) that now cause credential verification failure. OPEN

    (*** ACTION 2005-01-10--2 ***) Laurence Field or Markus Schulz to prototype a dump of the GOC database every few hours and provide a read-only copy for the community. OPEN

    (*** ACTION 2005-01-10--3 ***) The asian sites' support needs to be formalised. Requested by CERN at the relevant CIC-on-duty report. Not assigned to anyone. OPEN

    (*** ACTION 2005-02-07--1 ***) Nick & Flavia to send the procedure to be used by sites when they need to inform a VO that the SE fills-up to Piotr for publication in the Operations Manual. OPEN

    (*** ACTION 2005-02-07--2 ***) Helene and Markus to put the web page with CA rpms, currently under http://cern.ch/markusw, on the CIC web site. OPEN

    (*** ACTION 2005-02-07--3 ***) GOC database managers to add an operational days field, in addition to operational hours, e.g. Operational hours: 0900 - 1700 (GMT), for every site. Sites to correct their timezone in GOC db. OPEN

    (*** ACTION 2005-02-07--4 ***) Nick, on request from John Gordon and using some information circulated by Ian Bird to define metrics on site performance. OPEN

    AOB

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

    Maria Dimou, IT/GD, Grid Infrastructure Services

    There are minutes attached to this event. Show them.