Software Calendars
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
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.
(EMI 1) dCache v. 1.9.12
Support Calendar
End of Security Updates and Support of dCache v. 1.9.12 is scheduled on 31-08-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.
decommissioning Calendar
dCache v. 1.9.12 must be upgraded/retired by 31-08-2013 and no later than 30-09-2013 in compliance to the EGI Service Operations Security Policy (https://documents.egi.eu/document/669).
Operations Calendar dCache v. 1.9.12
- 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.
- Monitoring probe: eu.egi.sec.dCache-EMI-1,
EMI 1
Text below applies to all EMI 1 products with the exception of dCache 1.9.12.
Support Calendar EMI1
End of security updates and support: 30-04-2013 (http://www.eu-emi.eu/releases#MajRel)
Decommissioning Calendar EMI1
The EMI 1 decommissioning deadline is 01-05-2013.
Details:
- by 31-12-2013: new EMI 1 version probes are tested
- on 01-01-2013: EMI 1 version monitoring probes start returning WARNING
- on 01-03-2013: EMI 1 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Dashboard
- 30-04-2013: end of security updates and support of EMI 1
- 01-05-2013: EMI 1 decommissioning deadline
Operations Calendar EMI1
- Deployment of unsupported end-points is tracked by the EGI operations dashboard
- Monitoring probe documentation
- 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.
gLite 3.1 and gLite 3.2 products
Support Calendar gLite
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/) .
Decommissioning Calendar gLite
The products must be retired by 30-09-2012
Operations Calendar gLite
- Deployment of unsupported end-points is tracked by the EGI security dashboard
- Monitoring probe documentation
- 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 3.2 WN, DPM, LFC and dCache
Support Calendar gLite3.2
These products are now all unsupported (http://glite.cern.ch/R3.2/):
- glite-SE_dcache (end of security updates and support: 31/10/2011)
- glite-WN, glite-SE_dpm and glite-LFC (end of security updates and support: 30/11/2012).
Decommissioning Calendar gLite3.2
The services listed above must be decommissioned by 31-01-2013
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.
Operations Calendar gLite3.2
- Deployment of unsupported end-points is tracked by the EGI dashboard
- Monitoring probe documentation
- From the first week of December 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
- 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.