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 @


From EGIWiki
Jump to navigation Jump to search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators

General information



  • still working on CMD-OS updates
  • CMD-ONE first major to be released for OpenNebula 5
    • CESGA will update to OpenNebula 5 and test in particular the new cloudkeeper (former vmcatcher)


UMD 4.4.0 almost ready

  • CentOS7

Davix 0.6.4 GFAL 2.12.2 GFAL Utils 1.4.0 CGSI gSOAP 1.3.10 gfalFS 1.5.1 srm-ifce 1.24.1 FTS3 3.5.7 GRAM5 13.16.0 yaim core 5.1.4 GridFTP 11.8.1 MyProxy 6.1.25 globus-default-security 6.4.0 dCache SRM client 3.09.1 ARC 15.03.12 canL 2.2.8

  • SL6

VOMS Admin server 3.5.1 GFAL 2.12.2 GFAL Utils 1.4.0 CGSI gSOAP 1.3.10 gfalFS 1.5.1 FTS3 3.5.7 GRAM5 13.16.0 yaim core 5.1.4 Davix 0.6.4 GridFTP 11.8.1 MyProxy 6.1.25 globus-default-security 6.4.0 CGSI gSOAP 1.3.10 ARC 15.03.12 canL 2.2.8

  • pending: XrootD 4.6.0, fix for DPM 1.9.0 C7, Frontier
  • UMD 4.5 (May) will contain WN/UI for C7

Preview repository

released on 2017-02-15:


Decommissioning EMI WMS

As discussed at the last OMB, we are making plans for decommissioning the WMS and moving to DIRAC. We asked the NGIs (GGUS 126787) to provide statistics about the WMS usage in order to understand how much it is used and which VOs would be affected (and potentially interested) by this transition. Several NGIs have already provided some data, we are preparing a VOs list to contact.

Feedback from Helpdesk

IPv6 readiness plans

  • December OMB presentation: WLCG is going to deploy their services under dual-stack mode (v4+v6) by April 2018
  • EGI Operations started checking the core services against IPv6 compatibility
  • EGI Operations is going to assess the IPv6 readiness of the EGI infrastructure
  • early draft plan
    • Technology Providers: assess the IPv6 readiness of the middleware products
    • UMD team: perform verification of all services under IPv6 setup
    • EGI core services developers: assess the IPv6 readiness of the products
    • EGI core services hosts: assess the IPv6 readiness of the services
    • Resource Centres: assess the IPv6 readiness of the site infrastructure (real machines, cloud managers)
      • NGIs/ROCs please start discussing with sites and provide suggestions for the overall plan

Decommissioning of dCache 2.10

  • support for the dCache 2.10 ended at December 2016
  • according to EGI policies, dCache 2.10 must be decommissioned
  • broadcast sent on Feb2 + email sent on Feb7 to noc-managers mailing list
  • sites to upgrade their 2.10 endpoints to a newer "golden release" of dCache
    • 2.13, whose support ends on July 2017, which means in about 7 months from now, or
    • 2.16, whose support ends on May 2018: here take care that the dCache team does not support the upgrade from 2.10 directly to 2.16; only 2.10->2.13 and 2.13->2.16 transitions are supported.
  • decommissioning campaign will be started by EGI Operations to monitor the upgrade of the dCache 2.10 instances and follow up with the NGIs/sites; tickets will be opened this week
  • deadline is end of April, having all the sites more than 2 months to plan and perform the upgrade
  • probe will be WARNING for two months until April 17th, when it will switch to CRITICAL
  • in May EGI Operations will open tickets against sites still publishing dCache 2.10 and follow up on the upgrade plans
  • reference:

Testing the new webdav probes

Site Host GGUSID note
CYFRONET-LCG2 Registered
GR-01-AUTH Disabled
IGI-BOLOGNA Registered
INFN-T1,, Registered
NCG-INGRID-PT Registered
UKI-NORTHGRID-LIV-HEP Registered Registered

Testing of the storage accounting

As discussed during the January OMB, the APEL team would need one site per NGI for testing the storage accounting. The eligible sites are the ones providing either dCache or DPM storage elements.

More information can be found in the following wiki:

List of sites available for test.

Monthly Availability/Reliability

  • Underperformed sites in the past A/R reports with issues not yet fixed:
    • AsiaPacific GGUS 125427
      • TW-NCUHEP: site-bdii unstable
    • NGI_BG: GGUS 125826
      • BG05-SUGrid: failures in CAs and SRM probes, fixed some days ago
    • NGI_DE GGUS 125430
      • UNI-SIEGEN-HEP: waiting for the fix for CREAM probe.
    • NGI_NL: GGUS 123532
      • BelGrid-UCL: UNKNOWN status returned by CREAM probes, waiting for the fix for CREAM probe.
    • NGI_UA: GGUS 125839
      • UA-NSCMBR: ARC-CE failures, no progress yet
  • Underperformed sites after 3 consecutive months and underperformed NGIs:
    • AsiaPacific: GGUS 127024
      • KR-UOS-SSCC: there were srm problems, statistics are improving
    • NGI_AEGIS GGUS 127025
      • AEGIS11-MISANU: low A/R figures due to a bug in the emi.cream.CREAMCE-JobCancel probe, asked a recomputation
    • NGI_DE: GGUS 127026
      • wuppertalprod: issues with some ARC-CE passive probes that are not up-to-date, it could affect many sites
    • NGI_HR: GGUS 127027 (SOLVED)
      • it was partially decommissioned in December and management was transferred to a new team; statistics are improving.
    • NGI_PL: GGUS 127028 (SOLVED)
      • WUT: UNKNOWN status was solved by adding a WN to the ops queue

Monitoring of the UNCERTIFIED sites

Information about the proposal for using GOCDB as the only source of topology information for ARGO:

  • Timescale:
    • New GOC-DB release on Dec 7th including a boolean ‘monitored’ flag for the service endpoints: DONE
    • Then creation of a web UI view for uncertified sites in ARGO: DONE
    • Uncertified sites will be asked to fill in the service endpoints information. Follow the How to add URL service endpoint information into GOC-DB IN PROGRESS
    • As information is added in the GOCDB, uncertified sites/services will be picked up by the ARGO Monitoring Engine and they will start to be monitored DONE
    • By Q2 2017: support for multiple service endpoints

Nagios server for the uncertified sites:

  • Configuration is regenerated every hour
  • uncertified sites report on the ARGO development instance
  • IMPORTANT: for being correctly monitored, the uncertified sites have to fill in the proper services information into GOC-DB: please follow the HOWTO21

PROC09 modified accordingly.



Next meeting