Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

NGI DE CH Operations Center:Operations Meeting:17052013

From EGIWiki
Jump to navigation Jump to search

Operations Meeting Main

Mailing lists -> All NGI-DE/NGI-CH Site contacts


Kickoff of the DPM collaboration 
which will take over the coordination of the DPM project now that EMI is 

"The DPM Collaboration is happy to announce that it will take over 
coordination of the DPM project following the end of EMI. The 
collaboration represents major stakeholders in DPM who have all 
committed resources to maintaining, developing and supporting DPM as an 
efficient storage solution.

The agreement covers all aspects of the DPM project, including new 
dmlite developments, clients, and derived products such as the LFC and 
dynamic federations.

Beyond guaranteeing support for DPM for the communities represented in 
the collaboration, support will also be offered on a best-effort basis 
to other communities, along with the possibility of bilateral agreements 
and eventual membership for any wishing to contribute to the technology."
Dcache retirement calendar:
  • Meetings/conferences
  • Availability/reliability statistics
April: 97% 97%
UNI-BONN out of calculation
  • Monitoring
update 20

a problem with EMI-WN test for CE-SFT-Softver
reported to tools-admin list. Test hacked manually, so it works now
  • Staged rollout/updates
 UMD release 3.0.0
answer of Peter about, where is cream-LSF?:
the LSF module for CREAM is in the UMD-3 queue. The components is still in staged rollout and it didn't make for the UMD 3.0.0 deadline (this doesn't mean that it's failing the tests, but the EA did not have time to finish the staged rollout). Of course our goal is to release LSF module in the next update, if the early adopters will have time to finish the report.
Alternatively, to speed the process (and multiple reports are always advisable), if NGI_DE has sites who can act as early adopters I am glad to involve them in the process.

Round the sites

  • BMRZ-FRANKFURT (Uni Frankfurt)
running smoothly.
256 slots already at SL6 (as a test for vo queue) since autumn last year. Migration planed for all WNs in summer. Also switched from quator to puppet.
question about HEP-SPECS at SL6 
  • FZJuelich
would coordination of Unicore services in NGI-DE to make them fully productional
  • Goegrid
  • GSI
  • ITWM
Creams at UMD 3.0. What is about APEL?
CVMFS for LHCB-ok. for Atlas, mostly ok
  • KIT (GridKa, FZK-LCG2)
service at emi2/3
ongoing: dCache update to 2.2
  • KIT (Uni Karlsruhe)
  • LRZ
  • MPI-K
  • RWTH Aachen
  • SCAI
  • Uni Bonn
  • Uni Dortmund
  • Uni Dresden
  • Uni Freiburg
  • Uni Mainz-Maigrid
  • Uni Siegen
  • Uni Wuppertal
  • CSCS
  • PSI
  • Switch

Note: please update your entry at if needed.

Status ROD

false notes in tickets
+seems to be investigated.
20	 13.05	 19.05	 Team3, KIT	 switched
21	 20.05	 26.05	 Team5, LRZ	 (switched week 21/24)
22	 27.05	 02.06	 Team3, KIT	
23	 03.06	 09.06	 Team4, JUELICH	
24	 10.06	 16.06	 Team2, FhG (ITWM)	 (switched week 21/24)


what is about ROD next year after EGI??? A big question to discuss.