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 @

Difference between revisions of "Agenda-03-07-2017"

From EGIWiki
Jump to navigation Jump to search
Line 27: Line 27:

== Monthly Availability/Reliability  ==
== Monthly Availability/Reliability  ==
*Underperformed sites in the past A/R reports with issues not yet fixed:
**AfricaArabia: ZA-UCT-ICTS no improvement, no feedback, will be suspended after the meeting
***TW-NCUHEP: site-bdii unstable for network issues with ARGO
***KR-UOS-SSCC: there were srm problems, now also CREAM failures
**'''NGI_DE''' [ GGUS 125430]
***LRZ site-bdii unreachable, GRAM5 failures; improving
***UNI-SIEGEN-HEP: the fix for CREAM probes solved the issues, waiting the end of the month for closing
***wuppertalprod: the patch to the ARC-CE probes has been applied, the situation is improving
**NGI_FI: ARC-CE nagios probes bug
**NGI_UA: [ GGUS 125839]
***UA-NSCMBR: bug in the ARC-CE probes
***CA-MCGILL-CLUMEQ-T2: new problems regarding ssl on CREAM, they were solved, situation is improving
*Underperformed sites after 3 consecutive months and underperformed NGIs:
**AsiaPacific (MY-USM-GCL):
**NGI_CHINA: QoS violation (SOLVED)
**NGI_FRANCE: QoS violation
**NGI_IBERGRID (UNICAN) the site has just been decommissioned
**NGI_IL: QoS violation
**NGI_IT: QoS violation (SOLVED)
**NGI_UA: QoS violation (SOLVED)
**ROC_LA: QoS violation (SOLVED)

== Decommissioning EMI WMS  ==
== Decommissioning EMI WMS  ==

Revision as of 11:30, 19 June 2017

General information



  • CMD-OS 1.1.0 released (plus few updates to fix minor issues)
    • cloudkeeper-os and user_id policy enforcement patch for Mitaka will be released with an update, from Newton on the behaviour doesn't need patching


Preview repository



Testing FedCloud sites

Feedback from Helpdesk

yearly review of the information registered into GOC-DB

Monthly Availability/Reliability

Decommissioning EMI WMS

As discussed at the February and April/May OMBs, we are making plans for decommissioning the WMS and moving to DIRAC.

NGIs provided WMS usage statistics, and in general the usage is relatively low, mainly for local testing

Moderate usage by few VOs:

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

EGI contacted these VOs to agree a smooth migration of their activities to DIRAC, only some of them replied till now:

  • compchem is already testing DIRAC
  • discussing with the users the migration to DIRAC. Interested in a webinar on DIRAC.
  • mice: enabled on the GridPP DIRAC server

We need the VO feedback for better defining technical details and timeline:

  • NGIs with VOs using WMS (not necessarily limited to the VOs above), please contact them to ensure that these VOs have a back-up plan.

WMS servers can be decommissioned as soon as the supported VOs do not need them any more. The proposal is:

  • WMS will be removed from production starting from 1st January 2018.
    • VOs have 8 months to find alternatives or migrate to DIRAC
  • Considering that this is not an update, the decommission can be performed in few weeks.

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, tickets opened by EGI Operations to track decommissioning
  • dCache 2.13 decommissioning procedure started, in June the probes will get CRITICAL, support from dCache ends in July, upgrades to be performed by August
  • please upgrade to 2.16, whose support ends on May 2018, or to 3.0
    • 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.13 instances and follow up with the NGIs/sites at the beginning of August

Testing the new webdav probes

Site Host GGUSID note
INFN-T1 removed SOLVED

Missing steps:

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-06-12 UPDATE:

  • 26 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 March OMB, we are evaluating the creation of a new service type on GOC-DB that will be used for:
    • authorising the site/SE to publish the accounting data
    • making the site/SE appear in the portal
    • monitoring that the accounting data are regularly published

Currently the accounting service types are:

  1. glite-APEL: for authorizing the sending of the messages
  2. APEL: to monitor the accounting data publication

The proposed name is "APEL-SE"


Next meeting