NGI DE CH Operations Center:Operations Meeting:28092012
Jump to navigation Jump to search
- Minutes of last meeting
- Availability/reliability statistics
90% Three sites did not hit the target: RWTH-Aachen 52% UNI-SIEGEN-HEP 69% Source of this statistic is https://documents.egi.eu/public/RetrieveFile?docid=1332&version=2&filename=EGI_Aug2012.pdf
production update to release 17.1 still some problems with myegi web interface. For those sites which receive information for their local monitoring system should have a look. But the system works. All nodes are tested. Some problems with monitoring of WMSs, but should be fixed from now. Due to this the monitoring system was not available for two hours. But we will do a recomputation of the availability statistics
- Staged rollout/updates
gLite 3.1 ====== As already announced in  and in a number of other advisories, the gLite 3.1 distribution is now no longer supported (http://glite.cern.ch/R3.1/) and SL4 reached end of security support on 02/02/2012. Security patches for gLite 3.1 and SL4 are no longer available. Unsupported gLite 3.2 products ==================== The gLite 3.2 components currently out of security support are: APEL, ARGUS, BDII, Cluster, CREAM, dCache, LB, LSF utils, MPI utils, SCAS, SGE utils, Torque client/server/utils, VOMS . Decommissioning by 30-09-2012 ===================== gLite 3.1 products and *unsupported* gLite 3.2 software components have to be retired by 30-09-2012. Site managers can choose between the option of upgrading to a supported UMD release of the product  in consultation with the supported VOs, or the decommissioning of the service following the related procedure . Note well: this retirement calendar does not apply to gLite 3.2 products that are still supported. As already announced in , the support of glite 3.2 glite-UI, glite-WN, glite-GLEXEC_wn, glite-LFC_mysql/glite-LFC_oracle, glite-SE_dpm_disk/glite-SE_dpm_mysql was recently extended to 30/11/2012. Escalation ======= Starting from 01-10-2012 site managers of Resource Centres found to be hosting unsupported gLite 3.1/3.2 services, will be contacted through GGUS by the Central Grid Oversight team to request the retirement of the affected products. Resource Centres that will fail to retire unsupported gLite software by 01-11-2012, will be eligible for suspension and the problem will be escalated to EGI CSIRT for the enforcement of this suspension policy. EMI2 WN problem ======= Workernodes should not be updated to EMI2, because there are some troubles with this release.This was not officially announced. EMI 1 WN installation is not affected.
Round the sites
- BMRZ-FRANKFURT (Uni Frankfurt)
monitoring of https://ngi-de-unic.fz-juelich.de:9110/fzj-judge/services/TargetSystemFactoryService switched off as there is a ucc configuration problem at nagios site
- KIT (GridKa, FZK-LCG2, Dimitri Nilsen, Pavel Weber, Tobias Koenig)
most services to EMI1/2, except CREAM CEs and Apel. Apel still run gLite 3.2. We plan to update next week. We will be in contact via Email.
- KIT (Uni Karlsruhe)
- MPPMU (Cesare delle Fratte)
No EMI service already running at RZG EMI cream installation planned not before 2nd half of October
- RWTH Aachen
- SCAI (Andre Gemuend)
still working on the EMI updates. Priority to our SE is lower, because we migrate our data. Other services should be updated within the next two weeks.
- Uni Bonn
- Uni Dortmund
- Uni Dresden
- Uni Freiburg (Anton Gamel via Email)
After some Problems at the beginning of the month. torque 2.5.12 problem already mentioned), > that cost a _lot_ of availability/reliability % > site is doing well again. Started to deploy a xrootd cache machine > (xrd.bfg.uni-freiburg.de) User with lots of accesses of eos SRM > caused ban of some of our WNs at cern storage. Under investigation. State at the moment: root ./Analysis binary requests files not in > input list. Reason and "default path" unclear.
- Uni Mainz-Maigrid
- Uni Siegen
- Uni Wuppertal
Note: please update your entry at https://wiki.egi.eu/wiki/NGI_DE:Sites if needed.
- 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
If you have additional topics to be discussed during the meeting, please submit them in advance via our email list email list.
Next meeting will be in two or three weeks