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)


  • pending: XrootD 4.6.0
  • UMD 4.5 (May/June) will contain WN/UI for C7

Preview repository

released on:

  • 2017-03-28
    • Preview 1.10.1 AppDB info (sl6): VOMS-admin 3.6.0 (emergency release that fixes several vulnerabilities concerning voms-admin)


yearly review of the information registered into GOC-DB


On a yearly basis, the information registered into GOC-DB need to be verified. NGIs and RCs have been asked to check them. In particular:

  1. NGI managers should review the people registered and the roles assigned to them, and in particular check the following information:
    • E-Mail
    • ROD E-Mail
    • Security E-Mail
NGI Managers should also review the status of the "not certified" RCs, in according to the RC Status Workflow;
  1. RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:
    • E-Mail
    • telephone numbers
    • CSIRT E-Mail
RC administrators should also review the information related to the registered service endpoints.

The process should be completed by Apr 28th.

To track the process, a series of tickets have been opened.

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.

2017-04-10 UPDATE: VOs that we can try to contact:

  • NGI_CZ:
  • NGI_GRNET: see
  • NGI_IT:, compchem, theophys, virgo
  • NGI_PL: gaussian,, vo.nedm.cyfronet
  • NGI_UK: mice,

Feedback from Helpdesk

IPv6 readiness plans

    • 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 and 2.13

  • 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
  • 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:
  • STATUS: 8 instances still publishing 2.10

  • support for the dCache 2.13 will end on July 2017
  • date of starting the campaign: May 1st (-3m)
  • date of ending the campaign: Aug 31st (+1m)
  • to be announced at OMB and in the April EGI Monthly Broadcast

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

UPDATE 2017-04-10: this week the probes should be deployed on the ARGO test instance

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.

2017-04-10 UPDATE:

  • 25 sites are sending storage accounting data (only from dCache and DPM SEs). The data has to be verified before deploying the script in production.
  • After the discussion at the last OMB, we are evaluating the creation of a new service type for monitoring the publication of storage accounting data.
Currently the accounting service types are:
  1. glite-APEL: for authorizing the sending of the messages
  2. APEL: to monitor the accounting data publication

Monthly Availability/Reliability

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 DONE
    • 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.


  • VAPOR 2.2 released on March 16th
  • important for presenting the amount of computing and storage resources of the infrastructure
  • There are several improvements and new features: the computation of values of CPU and storages have been deeply reviewed, nevertheless some values are still not in line with the reality.

Next version will be focused on these computations to be able to provide better figures.

  • Please have a look at the information displayed and report us any inconsistency you should spot.

Proposal to modify the declaration of scheduled interventions

Currently (see MAN02 Service intervention management) scheduled interventions (of any duration) MUST be declared at least 24 hours in advance, specifying reason and duration; any intervention declared less than 24 hours in advance will be considered unscheduled.

WLCG proposed the following modification:

  • a scheduled intervention shorter than 5 days must be declared at least 24 hours in advance
  • a scheduled intervention longer than 5 days must be declared at least 1 month in advance
  • any other intervention that don't fulfill the rules above will be considered unscheduled

We are going to take a decision by the next OMB.


Next meeting