Difference between revisions of "NGI DE CH Operations Center:Operations Meeting:16032012"
Jump to navigation
Jump to search
Line 29: | Line 29: | ||
[[Operations_Surveys#Usage_and_future_maintenance_of_deployed_software|Usage and future maintenance of deployed software]] | [[Operations_Surveys#Usage_and_future_maintenance_of_deployed_software|Usage and future maintenance of deployed software]] | ||
[[Operations/Platform Deployment Survey]] | [[Operations/Platform Deployment Survey]] | ||
==Round the sites== | ==Round the sites== |
Revision as of 11:00, 16 March 2012
Introduction
- Minutes of last meeting
Announcements
- Meetings/conferences
- Availability/reliability statistics
Feb: VoOps: Av/Re= 97% UNI BONN=69% BDII: Av/Re=99,3%
- Monitoring
https://helpdesk.ngi-de.eu/index.php?mode=ticket_info&ticket_id=1969 https://helpdesk.ngi-de.eu/index.php?mode=ticket_info&ticket_id=1978
- Staged rollout/updates
UMD: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-13-17-02-2012
- Survey
Usage and future maintenance of deployed software Operations/Platform Deployment Survey
Round the sites
- NGI-DE
- BMRZ-FRANKFURT (Uni Frankfurt)
- DESY-HH
- DESY-ZN
- FZJuelich
- Goegrid
- GSI
- ITWM
09.03-> ITWM will not be able to attend the phone conference. There is nothing special to report.
- KIT (GridKa, FZK-LCG2)
9.03-> downtime 13.03 - 15.03, full site maintainance
- KIT (Uni Karlsruhe)
- LRZ
- MPI-K
- MPPMU
- 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
welcome LRZ Daniel Waldmann
- 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
09 27.02 04.03 Team5, LRZ 10 05.03 11.03 Team6, CSCS/NGI_CH 11 12.03 18.03 Team1, DESY 12 19.03 25.03 Team2, FhG
AOB
If you have additional topics to be discussed during the meeting, please submit them in advance via our email list email list.