Difference between revisions of "Software Calendars"
(→EMI 2) |
|||
(16 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Op menubar}} {{ | {{Template:Op menubar}} {{Template:Middleware_menubar}} | ||
[[ | |||
{{TOC_right}} | |||
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. | |||
= dCache v. 2.6.x = | |||
== Support calendar dCache v.2.6.x == | |||
End of Support for dCache v. 2.6.X: May 2015. | |||
== Decommissioning Calendar dCache 2.6.X == | |||
The dCache 2.6.X [[PROC16#Decommissioning_deadline|decommissioning deadline]] is 21-09-2015. Details: | |||
*'''31-08-2015''': dCache 2.6.X 2 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Dashboard | |||
*'''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. | |||
== Operations Calendar dCache v. 2.6.X == | |||
* 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 [https://operations-portal.egi.eu/dashboard site operations dashboard site operations dashboard]. | |||
**Site managers of Resource Centres found to be hosting dCache v. 2.6.X, will be contacted through GGUS by ROD to request the retirement/upgrade of the affected products. They should provide upgrade plans within 10 working days from the day the ticket is received | |||
*Monitoring probe: [[MW Nagios tests#eu.egi.sec.dCache-2.6|eu.egi.sec.dCache-2.6 documentation]] will be upgraded soon | |||
= dCache v. 2.2.X = | |||
== Support Calendar dCache v. 2.2.X == | |||
End of Support for dCache v. 2.2.X - July 2014, once hte new golden-release (2.10.X) is made available, according to [http://www.dcache.org/downloads/1.9/index.shtml Official dCache Releases & Release Policy page] | |||
== Decommissioning Calendar dCache 2.2.X == | |||
'''The dCache 2.2.X [[PROC16#Decommissioning_deadline|decommissioning deadline]] is 31-10-2014'''. | |||
Details: | |||
*on '''22-09-2014''': dCache 2.2.X 2 version monitoring probes start returning CRITICAL, alarms are displayed in the [https://operations-portal.egi.eu/dashboard Operations Dashboard] | |||
*'''31-10-2013''': dCache 2.2.X [[PROC16#Decommissioning_deadline|decommissioning deadline]] after this date all the dCache 2.2.X services must be decommissioned, upgraded to a supported version or in downtime. | |||
== Operations Calendar dCache v. 2.2.X == | |||
*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 [https://operations-portal.egi.eu/dashboard site operations dashboard]. | |||
**Site managers of Resource Centres found to be hosting dCache v. 2.2.X, will be contacted through GGUS by ROD to request the retirement/upgrade of the affected products. They should provide upgrade plans within 10 working days from the day the ticket is received | |||
*Monitoring probe: eu.egi.sec.dCache-2.2 [[MW Nagios tests#eu.egi.sec.dCache-2.2|documentation]] will be upgraded soon | |||
= EMI 2 = | |||
Text below applies to all EMI 2 products. | |||
== Support Calendar EMI2 == | |||
End of security updates and support: 30-04-2014 [http://www.eu-emi.eu/releases#MajRel (Official EMI page)] | |||
= | == Decommissioning Calendar EMI2 == | ||
'''The EMI 2 [[PROC16#Decommissioning_deadline|decommissioning deadline]] is 31-05-2014'''. | |||
Details: | |||
*by 01-03-2014: new EMI 2 version probes are tested returning WARNING | |||
* by 01-03-2014: new EMI 2 version probes are tested returning WARNING | *on 03-03-2014: EMI 2 version monitoring probes start returning CRITICAL, alarms are displayed in the [https://operations-portal.egi.eu/dashboard Operations Dashboard] | ||
* on 03-03-2014: EMI 2 version monitoring probes start returning CRITICAL, alarms are displayed in the [https://operations-portal.egi.eu/dashboard Operations Dashboard] | *30-04-2014: end of security updates and support of EMI 2 | ||
* 30-04-2014: end of security updates and support of EMI 2 | *31-05-2013: EMI 2 [[PROC16#Decommissioning_deadline|decommissioning deadline]] after this date all the EMI-2 services must be decommissioned, upgraded to a supported version or in downtime. | ||
* 31-05-2013: EMI 2 [[PROC16#Decommissioning_deadline |decommissioning deadline]] after this date all the EMI-2 services must be decommissioned, upgraded to a supported version or in downtime. | |||
== Affected middleware version == | == Affected middleware version == | ||
*ARC v2.* | *ARC v2.* | ||
*ARGUS v1.5.* | *ARGUS v1.5.* | ||
*BDII Site ''older'' than v1.2.0 | *BDII Site ''older'' than v1.2.0 | ||
*BDII Top ''older'' than v1.1.0 | *BDII Top ''older'' than v1.1.0 | ||
*CREAM v1.14.* | *CREAM v1.14.* | ||
*dCache v2.2.* | *dCache v2.2.* | ||
*DPM ''older'' than v1.8.6 | *DPM ''older'' than v1.8.6 | ||
*EMI-UI v2.* | *EMI-UI v2.* | ||
*EMI-WN v2.* | *EMI-WN v2.* | ||
*FTS v.2.2.8 | *FTS v.2.2.8 | ||
*StoRM ''older'' than v.1.11.0 | *StoRM ''older'' than v.1.11.0 | ||
*VOMS v.2.* | *VOMS v.2.* | ||
==Operations Calendar EMI2== | == Operations Calendar EMI2 == | ||
* Deployment of unsupported end-points is tracked by the EGI [https://operations-portal.egi.eu/dashboard operations dashboard] | |||
*Deployment of unsupported end-points is tracked by the EGI [https://operations-portal.egi.eu/dashboard operations dashboard] | |||
*Monitoring probe [[MW Nagios tests#Middleware_monitoring_SAM_instance|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 [https://operations-portal.egi.eu/dashboard 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. | |||
= (EMI 1) StoRM v. 1.8.3 = | |||
== Support Calendar == | |||
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. | |||
== Decommissioning Calendar == | |||
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. | |||
= (EMI 1) | = (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-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. | |||
== Decommissioning Calendar == | |||
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). | |||
= | == 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. | |||
dCache v. 1.9.12 | *Monitoring probe: eu.egi.sec.dCache-EMI-1 (see [[MW Nagios tests#Middleware_monitoring_SAM_instance|documentation]]) | ||
= | = EMI 1 = | ||
Text below applies to all EMI 1 products with the exception of dCache 1.9.12. | |||
Text below applies to all EMI 1 products with the exception of dCache 1.9.12. | |||
==Support Calendar EMI1== | == 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 [[PROC16#Decommissioning_deadline|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 [https://operations-portal.egi.eu/dashboard Operations Dashboard] | |||
*30-04-2013: end of security updates and support of EMI 1 | |||
*01-05-2013: EMI 1 [[PROC16#Decommissioning_deadline|decommissioning deadline]] | |||
== Operations Calendar EMI1 == | |||
*Deployment of unsupported end-points is tracked by the EGI [https://operations-portal.egi.eu/dashboard operations dashboard] | |||
*Monitoring probe [[MW Nagios tests#Middleware_monitoring_SAM_instance|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 [https://operations-portal.egi.eu/dashboard 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/) . | |||
=gLite | == 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 [https://operations-portal.egi.eu/csiDashboard security dashboard] | |||
*Monitoring probe [[MW Nagios tests#Security_SAM_instance|documentation]] | |||
* | |||
<br> | |||
* From | *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. | ||
* 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. | *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 [https://operations-portal.egi.eu/dashboard%7Coperations dashboard] | |||
*Monitoring probe [[MW Nagios tests#Middleware_monitoring_SAM_instance|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 [https://operations-portal.egi.eu/dashboard%7C 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. | |||
<br> | |||
= Retired software = | |||
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. | |||
{| border="1" | |||
|- style="background-color: lightgray;" | |||
| '''Provider''' | |||
| '''Release Notes/Updates''' | |||
| '''Support calendar''' | |||
| '''Release plan''' | |||
| '''Information''' | |||
|- | |||
| '''<div id="gLite">[[#gLite|gLite]]</div>''' | |||
| [http://glite.cern.ch/ Latest releases] | |||
| [http://tinyurl.com/gLitePatches Release Schedule] | |||
*[http://glite.cern.ch/support_calendar/ gLite 3.1 and 3.2] | |||
*'''gLite 3.1 IS RETIRED''' ([http://glite.cern.ch/R3.1/ gLite 3.1]) | |||
*gLite 3.2 [http://www.eu-emi.eu/support support policy] | |||
*gLite security updates: [https://twiki.cern.ch/twiki/bin/view/EGEE/GLiteSecUpdates process] | |||
| <!-- Next releases--> <br> | |||
| [http://go.egi.eu/glite32-patches gLite3.2 patches under development] | |||
*[http://glite.cern.ch/admin_documentation Installation and configuration] | |||
*[http://glite.cern.ch/R3.2/ gLite 3.2] | |||
*[http://glite.cern.ch/R3.1/ gLite 3.1] | |||
*[https://edms.cern.ch/document/722398/ gLite User Guide] <!--[https://twiki.cern.ch/twiki/bin/view/LCG/WLCGBaselineVersions WLCG baseline clients and services]--> | |||
|- | |||
| '''<div id="EMI">[[#EMI|EMI]]</div>''' | |||
| | |||
[http://www.eu-emi.eu/emi-3-montebianco EMI 3 Monte Bianco] | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/EMI3Updates EMI-3 Updates] | |||
[http://www.eu-emi.eu/emi-2-matterhorn EMI 2 Matterhorn] | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/EMI2Updates EMI-2 Updates] | |||
[http://www.eu-emi.eu/emi-1-kebnekaise EMI-1 Kebnekaise] | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/EMI1Updates EMI-1 Updates] | |||
| [http://www.eu-emi.eu/retirement-calendar EMI Support Calendar] | |||
[http://www.eu-emi.eu/releases#MajRel EMI Support Policy] [http://www.eu-emi.eu/releases EMI Release Policy] | |||
[http://www.eu-emi.eu/support EMI Incident Handling Policy] | |||
| <br> | |||
| | |||
*[https://twiki.cern.ch/twiki/pub/EMI/DeliverableDSA11/EMI-DSA1.1-1277556-Software_Maintenance_Support_Plan-v1.0.pdf EMI Software Maintenance and Support Plan] | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDNA133 DNA1.3.3 Technical Development Plan] (PY3) | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA113 DJRA1.1.3 Compute Area Work Plan and Status Report] (PY3) <!--** [https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1T2Compute Status of implementation]--> | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA123 DJRA1.2.3 Data Area Work Plan and Status Report] (PY2) <!--** [https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1T3DataDJRA123 Status of implementation]--> | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA133 DJRA1.3.3 Security Area Work Plan and Status Report] (PY2) | |||
**[https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1T4Security Status of implementation] | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA143 DJRA1.4.3 Infrastructure Area Work Plan and Status Report] (PY2) | |||
**[https://twiki.cern.ch/twiki/bin/view/EMI/InfrastructureArea Status of implementation] | |||
*[https://twiki.cern.ch/twiki/bin/view/EMI/EmiDeliverables All deliverables] | |||
*EMI [https://twiki.cern.ch/twiki/bin/view/EMI/EMTSrcTemplate#SrcLinks Service Cards] | |||
*''DRAFT'' EMI's CEs [http://www.nordugrid.org/arc/ce/chart.html comparison chart] | |||
|- | |||
| '''<div id="IGE">[[#IGE|IGE]]</div>''' | |||
| | |||
[https://sites.google.com/a/ige-project.eu/public/downloads/software/releases Release notes] | |||
| [https://wiki.egi.eu/wiki/File:IGE_Support_Schedule.pdf IGE support calendar (file)] | |||
| <br> | |||
| [http://www.ige-project.eu/hub/rt Instructions] to submit requirement to IGE | |||
[http://rt.ige-project.eu/rt/Search/Results.html?Query=Queue%20%3D%20%27Change%2FRequirements%20Requests%27%20AND%20%28Status%20%3D%20%27new%27%20OR%20Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27stalled%27%29 IGE Requirements] | |||
|} | |||
<br> | |||
[[Category:Middleware]] |
Latest revision as of 19:57, 7 May 2015
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.
dCache v. 2.6.x
Support calendar dCache v.2.6.x
End of Support for dCache v. 2.6.X: May 2015.
Decommissioning Calendar dCache 2.6.X
The dCache 2.6.X decommissioning deadline is 21-09-2015. Details:
- 31-08-2015: dCache 2.6.X 2 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Dashboard
- 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.
Operations Calendar dCache v. 2.6.X
- 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.
- Site managers of Resource Centres found to be hosting dCache v. 2.6.X, will be contacted through GGUS by ROD to request the retirement/upgrade of the affected products. They should provide upgrade plans within 10 working days from the day the ticket is received
- Monitoring probe: eu.egi.sec.dCache-2.6 documentation will be upgraded soon
dCache v. 2.2.X
Support Calendar dCache v. 2.2.X
End of Support for dCache v. 2.2.X - July 2014, once hte new golden-release (2.10.X) is made available, according to Official dCache Releases & Release Policy page
Decommissioning Calendar dCache 2.2.X
The dCache 2.2.X decommissioning deadline is 31-10-2014.
Details:
- on 22-09-2014: dCache 2.2.X 2 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Dashboard
- 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.
Operations Calendar dCache v. 2.2.X
- 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.
- Site managers of Resource Centres found to be hosting dCache v. 2.2.X, will be contacted through GGUS by ROD to request the retirement/upgrade of the affected products. They should provide upgrade plans within 10 working days from the day the ticket is received
- Monitoring probe: eu.egi.sec.dCache-2.2 documentation will be upgraded soon
EMI 2
Text below applies to all EMI 2 products.
Support Calendar EMI2
End of security updates and support: 30-04-2014 (Official EMI page)
Decommissioning Calendar EMI2
The EMI 2 decommissioning deadline is 31-05-2014.
Details:
- by 01-03-2014: new EMI 2 version probes are tested returning WARNING
- on 03-03-2014: EMI 2 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Dashboard
- 30-04-2014: end of security updates and support of EMI 2
- 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.
Affected middleware version
- ARC v2.*
- ARGUS v1.5.*
- BDII Site older than v1.2.0
- BDII Top older than v1.1.0
- CREAM v1.14.*
- dCache v2.2.*
- DPM older than v1.8.6
- EMI-UI v2.*
- EMI-WN v2.*
- FTS v.2.2.8
- StoRM older than v.1.11.0
- VOMS v.2.*
Operations Calendar EMI2
- Deployment of unsupported end-points is tracked by the EGI operations dashboard
- 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.
(EMI 1) StoRM v. 1.8.3
Support Calendar
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.
Decommissioning Calendar
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.
(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-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.
Decommissioning Calendar
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).
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 (see documentation)
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.
Retired software
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.
Provider | Release Notes/Updates | Support calendar | Release plan | Information |
Latest releases | Release Schedule
|
gLite3.2 patches under development | ||
EMI Support Calendar |
| |||
IGE support calendar (file) | Instructions to submit requirement to IGE |