Source: https://wiki.egi.eu/wiki/Software_Retirement_Calendar
Timestamp: 2019-04-26 14:37:36+00:00

Document:
This page provides an overview of the timing and operations steps for the retirement of grid middleware that either already reached end of security updates and support or that is about to reach this status.
End of Support for dCache v. 2.6.X: May 2015.
21-09-2015: dCache 2.6.X decommissioning deadline - after this date all the dCache 2.6.X services must be decommissioned, upgraded to a supported version or in downtime.
From 31-08-2015: Nagios probes will detected unsupported service end-points according to the version information available from BDII. Probes detecting unsupported service end-points, will generate alarms that can be tracked by administrators on the site operations dashboard site operations dashboard.
The dCache 2.2.X decommissioning deadline is 31-10-2014.
31-10-2013: dCache 2.2.X decommissioning deadline after this date all the dCache 2.2.X services must be decommissioned, upgraded to a supported version or in downtime.
From 22-09-2014 Nagios probes (run by a dedicated EGI instance of SAM) will detected unsupported service end-points according to the version information available from BDII. Probes detecting unsupported service end-points, will generate alarms that can be tracked by administrators on the site operations dashboard.
Text below applies to all EMI 2 products.
The EMI 2 decommissioning deadline is 31-05-2014.
31-05-2013: EMI 2 decommissioning deadline after this date all the EMI-2 services must be decommissioned, upgraded to a supported version or in downtime.
Monitoring probe documentation will be upgraded soon.
From 03-03-2014 Nagios probes (run by a dedicated EGI instance of SAM) will detected unsupported service end-points according to the version information available from BDII - where possible. Probes detecting unsupported service end-points, will generate alarms that can be tracked by administrators on the site operations dashboard.
After 03-03-2014 administrators of the affected Resource Centres will receive notification tickets, and will be requested to provide information about their upgrade plans within 10 working days from the day the ticket is received.
StoRM 1.11.1 was released in UMD-3. StoRM 1.8.3 security support ends on July 15 2013.
End of security updates of StoRM was scheduled after three weeks of the complete and successful process of staged rollout for a version of StoRM for UMD-3.
StoRM 1.8.3 or older versions must be upgraded to a supported release within one month after the end of security support of the EMI-1 version 1.8.3.
The current version of StoRM available in UMD-3 (v.1.11.1) has performance issues, and currently the installation of this version is discouraged. Without a replacement for the EMI-1 version, the deadline for the decommission of EMI-1 StoRM is currently not fixed. It will be updated once the patch is available in UMD.
Monitoring tests which identify StoRM production instances which reach end of support are now raising warnings in the midmon nagios instance.
End of Security Updates and Support of dCache v. 1.9.12 is scheduled on 31-09-2013. dCache v. 1.9.12 is part of the EMI-1 release, and the end of Security Updates and Support was previously scheduled on 30-04-2013. Security Updates and Support only provides updates targeting security vulnerabilities. dCache v. 1.9.12 will not get SHA2 support back-ported. EGI and dCache.org will make a separate announcement on the roadmap for SHA2 support in dCache.
dCache v. 1.9.12 must be upgraded/retired by 30-09-2013 and no later than 30-10-2013 in compliance to the EGI Service Operations Security Policy (https://documents.egi.eu/document/669).
From 01-07-2013 site managers of Resource Centres found to be hosting dCache v. 1.9.12, will be contacted through GGUS by ROD to request the retirement of the affected products.
Text below applies to all EMI 1 products with the exception of dCache 1.9.12.
The EMI 1 decommissioning deadline is 01-05-2013.
From 01-03-2013 Nagios probes (run by a dedicated EGI instance of SAM) will detected unsupported service end-points according to the version information available from BDII - where possible. Probes detecting unsupported service end-points, will generate alarms that can be tracked by administrators on the site operations dashboard.
After 01-03-2013 administrators of the affected Resource Centres will receive notification tickets, and will be requested to provide information about their upgrade plans within 10 working days from the day the ticket is received.
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.
The follorwing gLite 3.2 components are out of security support: APEL, ARGUS, BDII, Cluster, CREAM, dCache, LB, LSF utils, MPI utils, SCAS, SGE utils, Torque client/server/utils, VOMS (http://glite.cern.ch/R3.2/) .
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.
From 01-11-2012 Resource Centres that will fail to retire unsupported gLite software, do not put the affected service end points in scheduled downtime, and do not provide information about their upgrade plans will be eligible for suspension and the problem will be escalated to EGI CSIRT.
glite-WN, glite-SE_dpm and glite-LFC (end of security updates and support: 30/11/2012).
Service end-points which can not be upgraded by this deadline, must be set in downtime as of 01-02-2013, unless upgrading is not possible for technical reasons.
Administrators of the affected Resource Centres will receive notification tickets, and are requested to provide information about their upgrade plans within 10 working days from the day the ticket is received.
gLite 3.1 and 3.2 are both retired with the only exception of glite-VOBOX for which only Security Updates are granted until 30/04/2013.
This page was last modified on 7 May 2015, at 17:57.

References: v. 
 v. 
 v. 
 v. 
 v. 
 v.