Difference between revisions of "NGI DE CH Operations Center:Operations Meeting:14092012"
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
* Meetings/conferences | * Meetings/conferences | ||
EGI: next week Technical Forum Prague | EGI: next week there is the Technical Forum in Prague | ||
* Availability/reliability statistics | * Availability/reliability statistics | ||
https://documents.egi.eu/public/RetrieveFile?docid=1332&version=2&filename=EGI_Aug2012.pdf | https://documents.egi.eu/public/RetrieveFile?docid=1332&version=2&filename=EGI_Aug2012.pdf | ||
Line 14: | Line 14: | ||
90% | 90% | ||
Three sites not hit the target: | Three sites did not hit the target: | ||
RWTH-Aachen 68% | RWTH-Aachen 68% | ||
UNI-FREIBURG 59% | UNI-FREIBURG 59% | ||
Line 20: | Line 20: | ||
* Monitoring | * Monitoring | ||
update 17 tested. Update 17 include sensors for Globus, Unicore and EMI 2 WNs | update 17 tested. It seems to work fine. Next week we update our production system. Update 17 include sensors for Globus, Unicore | ||
and EMI 2 WNs | |||
* Staged rollout/updates | * Staged rollout/updates | ||
Line 36: | Line 37: | ||
Sites that support WLCG VOs should update to EMI release until 1st October. At least to EMI 1. gLite releases should not longer be | Sites that support WLCG VOs should update to EMI release until 1st October. At least to EMI 1. gLite releases should not longer be | ||
supported. We at KIT are currently updating our services (WMSs, sBDIIs, CREAMs). WNs will follow. Dimitri will send around a list | supported. We at KIT are currently updating our services (WMSs, sBDIIs, CREAMs). WNs will follow. Dimitri will send around a list | ||
of versions. 1st October will be unrealistic. | of versions and deadlines. 1st October will be a little bit unrealistic. | ||
==Round the sites== | ==Round the sites== |
Revision as of 13:15, 20 September 2012
Introduction
- Minutes of last meeting
Announcements
- Meetings/conferences
EGI: next week there is the Technical Forum in Prague
- Availability/reliability statistics
https://documents.egi.eu/public/RetrieveFile?docid=1332&version=2&filename=EGI_Aug2012.pdf
90% Three sites did not hit the target: RWTH-Aachen 68% UNI-FREIBURG 59% UNI-SIEGEN-HEP 31%
- Monitoring
update 17 tested. It seems to work fine. Next week we update our production system. Update 17 include sensors for Globus, Unicore and EMI 2 WNs
- Staged rollout/updates
DN Publishing -----Ursprüngliche Nachricht----- Von: Operations of NGI-DE [1] Im Auftrag von Dimitri Nilsen Gesendet: Dienstag, 31. Juli 2012 18:20 An: NGI-DE-OPERATIONS@LISTSERV.DFN.DE Betreff: Publishing User DNs Dear Sites, according to "Grid Policy on the Handling of User-Level Job Accounting Data" sites should publish User DNs for accounting Please ensure you have publishGlobalUserName="yes" in publisher-config.xml at your apel box
Status of releases Sites that support WLCG VOs should update to EMI release until 1st October. At least to EMI 1. gLite releases should not longer be supported. We at KIT are currently updating our services (WMSs, sBDIIs, CREAMs). WNs will follow. Dimitri will send around a list of versions and deadlines. 1st October will be a little bit unrealistic.
Round the sites
- NGI-DE
- BMRZ-FRANKFURT (Uni Frankfurt)
- DESY-HH
- DESY-ZN
- FZJuelich
- Goegrid
- GSI
- ITWM
- all WNs and CEs updated to SL6 and EMI-2/UMD-2 - one SE node, APEL node, site BDII still running glite 3.2 - What is the status of this EGI broadcast?
- KIT (GridKa, FZK-LCG2)
- KIT (Uni Karlsruhe)
emi migration. plans to update WN to EMI 2. any experience whit emi-wn?
- LRZ
- MPI-K
- MPPMU
- deployement of CVMFS
- RWTH Aachen
- SCAI
- Uni Bonn
- Uni Dortmund
- Uni Dresden
- Uni Freiburg
- Uni Mainz-Maigrid
- Uni Siegen
- Uni Wuppertal
- SwiNG
- CSCS
- PSI
- Switch
Note: please update your entry at https://wiki.egi.eu/wiki/NGI_DE:Sites if needed.
Status ROD
- Any problematic tickets?
- Handover of the ROD shift
- ROD shift schedule https://wiki.egi.eu/wiki/NGI_DE_CH_Operations_Center:Operations_Teams#Shifts_rotation_table
AOB
If you have additional topics to be discussed during the meeting, please submit them in advance via our email list email list.