PASTE meeting

→ Europe/Zurich
1/1-025 (CERN)

1/1-025

CERN

20
Show room on map
Andrei Tsaregorodtsev
Description
CERN, bat 2 R-030 To join the telephone conference, click here: https://audioconf.cern.ch/call/0165202 To dial in to the conference: a. Dial +41 22 7676000 b. Enter access code 0165202
Production and PASTE Meeting, 19th August 2008, CERN Chair: A.Tsaregorodtsev Minutes: S. Paterson CERN: P.Charpentier, J.Closier, S.Paterson, R.Santinelli Phone: R.Bernet, R.Nandakumar, A.Tsaregorodtsev Apologies: N.Brook, A.C.Smith 0. Ongoing Action List (07) - 27/11/07 - Zoltan, Elisa - Prototype bookkeeping system, roadmap for production (09) - 04/12/07 - Roberto, Marcos - Develop a general service monitoring framework leading to a virtual control room (57) - 24/06/08 - Vladimir - Automatic publishing of BDII information in the CS using GOCDB site names (62) - 22/07/08 - Roberto - Check whether glite 3.1 comes with requested features/patches & coordinate upgrades (63) - 22/07/08 - Roberto,Joel - Develop DIRAC3 script for adding new users to the VO + CS + LFC registration (65) - 05/08/08 - Roberto - Define our SAM tests in the dashboard (68) - 05/08/08 - Zoltan - Migrate new BK from volhcb07 -> volhcb04 (69) - 12/08/08 - Joel - All the sites to provide single user account for the sgm user (70) - 12/08/08 - Joel - DIRAC3 installation in the LHCb release area at CERN (71) - 19/08/08 - Andrei,Joel - Add comment field to mask operations and formulate procedure (72) - 19/08/08 - Roberto,Vladimir - Check BDII / GOCDB inconsistencies in site published informations (73) - 19/08/08 - Andrei - Resolve BK catalogue status problems in the Replica Manager (74) - 19/08/08 - Joel - Create list of host aliases attached to the agenda of last week (75) - 19/08/08 - Stuart,Vladimir - Make command line tools for managing LHCb Software (00) - 19/08/08 - DIRAC developers - DIRAC3 (ongoing) Completed Actions: Done - (59) - 22/07/08 - Ricardo - Add ldap python modules to DIRAC python distribution Done - (64) - 29/07/08 - Philippe, Andrew - Prepare SRMv1 retirement migration plan Done - (66) - 05/08/08 - Vladimir - Investigate interfaces to GOC DB for site downtime (c.f. ATLAS Dashboard) Done - (67) - 05/08/08 - Andrei - Test failover request forwarding mechanism 1. Action Updates - Action(07) - Prototype Bookkeeping Zoltan is back on Wednesday. - Action(09) - Virtual Control Room SAM test status now being reported weekly to the Tier-1 sites (to explain low results). SAM test visualization for the Tier-0, Tier-1 and Tier-2 sites via the Dashboard is pending. The Tier-1 VO-box test will be integrated into this suite. The Google calendar is in place, Stuart suggested categorizing the items via Tier and downtime time e.g. scheduled, unscheduled. There was some discussion regarding the procedure for banning and unbanning sites, Andrei agreed to add a comment field and Joel agreed to formulate the procedure. ( ACTION: Andrei, Joel ) - Action(57) - Automatic publishing of BDII information in the CS It was mentioned that some sites are presenting inconsistent information in the BDII / GOC DB Roberto agreed to go over this with Vladimir. ( ACTION: Roberto ) - Action(62) - Check whether glite 3.1 comes with requested features/patches & coordinate upgrades Roberto will send a summary via mail. - Action(63) - DIRAC3 scripts for adding new users to the VO + CS + LFC registration Roberto found some problems with this script and is in the process of converting it to python. - Action(64) - Preprare SRMv1 retirement plan This was compiled and is attached to the agenda. It was agreed to update the attached plan with the changes as discussed during the meeting. - Action(69) - Single user account for SGM user Joel is proceeding through the sites requesting single accounts for SGM users. - Action(70) - DIRAC3 installation in the LHCb release area at CERN It was agreed to enable write permission to the DIRAC configuration file for the DIRAC developers in case of emergencies. 2. Production Issues The DIRAC2 test machine (lxgate03) and DIRAC2 DMS (lxgate34) can now be retired. There was some discussion regarding the communication between the Operations team and the DIRAC developers and it was suggested to clean up the old Savannah page. Joel commented that there was a very old DIRAC Savannah project that can be used for this and confirmed that the administrators from the DIRAC2 project are added there. - Report from the Production meeting Stuart mentioned that the BK replica flag was not set in recent tests, after setting the status of the BK catalog to 'Active' there were problems with normal put and register operations, e.g. all putAndRegister operations try to set a 'has replica' flag in the BK catalog. After some discussion it was agreed to pursue a temporary solution of changing the configuration setting of BK to 'InActive' in the CS by default ( ACTION: Andrei ). A feature request should be formulated to afford this option in the constructor of the Replica Manager in the future. Recent SAM jobs at CERN cannot write into shared area, ongoing issue being debugged. - Ancestor file treatment at job creation, submission Tests are ongoing and this will be discussed presently. It was noted that not all of the Tier-1 '-tape' SEs are defined in the CS, these will be added immediately. - DIRAC host aliases It was agreed to take the list of updated aliases from last week and allow these as soon as possible. ( ACTION: Joel ) - DIRAC2 distribution with recent fixes in modules, SRMStorage There was some discussion on the recent reversion of CVS commit privileges that is still not understood. It was agreed to commit the recent changes to DIRAC2 and make a release. 3. DIRAC3 Tasks - Workflow module coding conventions Discussions will continue via mailing lists. - Job creation strategy in the Production DB Creation and submission strategy of jobs has changed after recent ancestor file considerations. Population of the ProductionDB from the BK / LFC information vastly reduces the risk of inconsistency. - Application software description in CS Command line tools should be created to manage the list of LHCb software. ( ACTION: Stuart, Vladimir ) 4. AOB None
There are minutes attached to this event. Show them.
    • 09:30 → 09:50
      Ongoing actions 20m
      (07) - 27/11/07 - Zoltan, Elisa - Prototype bookkeeping system on volhcb07 (09) - 04/12/07 - Roberto, Marcos - Develop a general service monitoring framework leading to a virtual control room (57) - 24/06/08 - Vladimir - Automatic publishing of BDII information in the CS using GOCDB site names (59) - 22/07/08 - Ricardo - Add ldap python modules to DIRAC python distribution (62) - 22/07/08 - Roberto - Check whether glite 3.1 comes with requested features/patches & coordinate upgrades (63) - 22/07/08 - Roberto,Joel - Develop DIRAC3 script for adding new users to the VO + CS + LFC registration (64) - 29/07/08 - Philippe, Andrew - Prepare SRMv1 retirement migration plan (65) - 05/08/08 - Roberto - Define our SAM tests in the dashboard (66) - 05/08/08 - Vladimir - Investigate interfaces to GOC DB for site downtime (c.f. ATLAS Dashboard) (67) - 05/08/08 - Andrei - Test failover request forwarding mechanism (68) - 05/08/08 - Zoltan - Migrate new BK from volhcb07 -> volhcb04 (69) - 12/08/08 - Joel - All the sites to provide single user account for the sgm user (70) - 12/08/08 - Joel - DIRAC3 installation in the LHCb release area at CERN (00) - 05/08/08 - DIRAC developers - DIRAC3 (ongoing)
      SRMv1 migration plan
    • 09:50 → 10:05
      Production status report 15m
      - Report from the Production meeting - Bookkeeping update testing in DIRAC3 production - Ancestor file treatment at job creation, submission - DIRAC host aliases - DIRAC2 distribution with recent fixes in modules, SRMStorage
    • 10:05 → 10:35
      DIRAC3 tasks 30m
      - Workflow module coding conventions - Job creation strategy in the Production DB - Application software description in CS
    • 10:35 → 10:45
      AOB 10m