General information

• the Operations meeting will be on the 2nd Monday of the month
• the EGI Operations Meeting schedule for first half of 2016 is available on Indico: https://indico.egi.eu/indico/categoryDisplay.py?categId=32 and on the new summary page: https://wiki.egi.eu/wiki/Operations_Meeting

UMD/CMD

• UMD 3.14.3 to be released, fixing problem with gpgkeys, urgent
• UMD 3.14.2 released http://repository.egi.eu/2016/06/16/release-umd-3-14-2/
  • StoRM 1.11.11, dCache 2.10.56, edg-mkgrid 4.0.3 (fix), Globus Network Manager on SL6

• UMD 4.1.1 released on 27-06-2016
  • edg-mkgrid 4.0.3 (missing), Globus Network Manager on SL6

• UMD 4.2.0 to be released by July
  • including on CentOS7: FTS3, QCG, dCache, ARGUS
  • include on CentOS7 if possible: DPM, Globus/GFAL (fix issue with udt driver)
  • add regular updates on SL6

Preview repository

• 2016-07-07:
  • Preview 2.3.0 AppDB info (CentOS 7): release fix for ARGUS 1.7.0

• 2016-06-20:
  • Preview 1.3.0 AppDB info (sl6)
  • Preview 2.2.0 AppDB info (CentOS 7)

Generic information about Preview repository: https://wiki.egi.eu/wiki/Preview_Repository

Note: EGI provides the preview repository without any additional quality assurance process, but the products are released as they are provided by the product team. EGI recommends the use of the UMD repositories, which contain software verified through the quality assurance process of UMD.

Operations

EGI central monitoring instance (ARGO)

Since July 1st, the EGI infrastructure is being monitored by two monitoring instances that can be found on these addresses:

https://argo-mon.egi.eu/nagios https://argo-mon2.egi.eu/nagios

Both instances are running the same set of tests and results provided are equivalent.

Starting from the same date, the central ARGO Web UI (http://argo.egi.eu/lavoisier ) provides information from these two instances and the Operations Portal was reconfigured to raise alarms based on information from ARGO central instances.

Results coming from NGI SAM instances are no longer consumed by the central ARGO or Operations Portal so NGIs can eventually decommission them following the standard decommissioning procedures (https://wiki.egi.eu/wiki/PROC12 ).

The FedCloud sites will be monitored by the new system starting from Aug 1st.

New set of CREAM probes

A new set of probes is being used for monitoring the CREAM CEs and the A/R computation: https://wiki.italiangrid.it/twiki/bin/view/CREAM/DjsCreamProbeNew This set of probe doesn't make use of the BDII, WMS and the messaging infrastructure like instead did the old WN monitoring framework.

RFC proxy will be default

• moving to RFC proxy instead of legacy proxy
• in production since a while, everybody is using RFC
• we will ask VOMS TP to make a little modification on VOMS client, changing the default

New configuration for DTEAM VO

The HellasGrid Certification Authority changed its DN from "/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006" to "/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016"

Since it is also changed the certificate of the 2 voms servers hosting dteam VO, the settings of this VO need to be updated accordingly on *ALL THE (grid and cloud) SERVICES*

- New yaim settings (for the ../vo.d/dteam file):

VOMS_SERVERS='vomss://voms.hellasgrid.gr:8443/voms/dteam?/dteam/'
VOMSES="'dteam voms.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr dteam 24' 'dteam voms2.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr dteam 24'"
VOMS_CA_DN="'/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016' '/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016'"

- .lsc files:

# cat /etc/grid-security/vomsdir/dteam/voms.hellasgrid.gr.lsc
/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr
/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

# cat /etc/grid-security/vomsdir/dteam/voms2.hellasgrid.gr.lsc
/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr
/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

- configuration information:

https://voms.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action https://voms2.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action

Monthly Availability/Reliability

A/R report on ARGO: http://argo.egi.eu/lavoisier/ngi_reports?accept=html

List of the underperforming RCs for (at least) 3 consecutive months:

• AfricaArabia https://ggus.eu/?mode=ticket_info&ticket_id=117094: main problems with the monitoring system, waiting for the release of the central one
  • ASRT
  • EG-ZC-T3: unresponsive since too months, must be suspended
  • ZA-UJ

• AsiaPacific: (since February) https://ggus.eu/index.php?mode=ticket_info&ticket_id=121222
  • KR-UOS-SSCC
  • MY-UPM-BIRUNI-01

• CERN: https://ggus.eu/index.php?mode=ticket_info&ticket_id=122596 SRM issues

• NGI_DE: https://ggus.eu/?mode=ticket_info&ticket_id=121975
  • UNI-SIEGEN-HEP: flapping behaviour

• NGI_IBERGRID: https://ggus.eu/index.php?mode=ticket_info&ticket_id=122599 (SOLVED)
  • UB-LCG2 site suspended

'* NGI_MARGI https://ggus.eu/index.php?mode=ticket_info&ticket_id=118465 no monitoring data since January

• NGI_NL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=122607 (SOLVED)
  • EENet: site suspended

• NGI_PL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=122611 (SOLVED) monitoring data missing for:
  • ICM
  • IFJ-PAN-BG

• NGI_RO: https://ggus.eu/index.php?mode=ticket_info&ticket_id=122612
  • RO-14-ITIM miscellaneous issues, site is recovering

• NGI_UA: https://ggus.eu/index.php?mode=ticket_info&ticket_id=122613 (SOLVED)
  • UA_KNU: many power cuts

• Russia: https://ggus.eu/index.php?mode=ticket_info&ticket_id=122615
  • Ru-Troitsk-INR-LCG2

Decommissioning SL5

• Tracked on SL5_retirement wiki
• Sites still deploying unsupported service end-points risk suspension, unless documented technical reasons prevent a Site Admin from updating these end-points https://wiki.egi.eu/wiki/PROC16_Decommissioning_of_unsupported_software#Escalation_phase see step 7
• Status https://wiki.egi.eu/wiki/SL5_retirement#2016-06-13_Overall_status reported below.
• from this week on EGI Operations can suspend sites that host SL5 services in production and not set under downtime
  • tickets will be opened

Status and actions (Jul 14th)

• 1 Top-BDII bdii.hpgcc.finki.ukim.mk
• 11 Site-BDII apel.indiacms.res.in arc.hpc-mhi.org ce-enmr.chemie.uni-frankfurt.de ce.hpgcc.finki.ukim.mk ce01.grid.etf.rtu.lv glite-bdii.scai.fraunhofer.de is.biruni.upm.my sbdii.grid.uni-sofia.bg uagrid.org.ua uosaf0006.sscc.uos.ac.kr west.icmp.lviv.ua
• 4 MyProxy kek2-px.cc.kek.jp myproxy.cat.cbpf.br wipp-rb.weizmann.ac.il
• 7 WMS and 6 LB glite-wms.scai.fraunhofer.de graspol.nikhef.nl graszode.nikhef.nl graskant.nikhef.nl grasveld.nikhef.nl lb.biruni.upm.my kek2-wms.cc.kek.jp kek2-lb.cc.kek.jp mb-enmr.chemie.uni-frankfurt.de marwmsmr.in2p3.fr (downtime)
• 1 VOMS glite-io.scai.fraunhofer.de
• 1 ARGUS argus.indiacms.res.in
• 7 CREAM-CE ce-enmr.chemie.uni-frankfurt.de ce.hpgcc.finki.ukim.mk ce2.particles.ipm.ac.ir glite-cream.scai.fraunhofer.de haitham.biruni.upm.my kek2-ce01.cc.kek.jp razi.biruni.upm.my
• 0 QCG Computing
• 1 STORM grid-se2.pr.infn.it (downtime)

RCs about to be suspended

FedCloud status

AOB

Next meeting

• 08th Aug 2016 https://indico.egi.eu/indico/event/3004/ -> cancelled in favour of 12 September https://indico.egi.eu/indico/event/3005/
• new calendar available until end of 2016 https://indico.egi.eu/indico/category/32/