Software Calendars

From EGIWiki
Revision as of 12:58, 14 January 2013 by Tferrari (talk | contribs) (Created page with "{{Template:Op menubar}} {{TOC_right}} {{Template:Middleware_menubar}} Category:Middleware = gLite 3.1 and other gLite 3.2 products = ==Support Calendar== The gLite 3.1 dist...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security



Middleware menu: Home Software Calendars Technology Providers UMD Release Schedule UMD Products Overview UMD Products ID Cards Release and deployment process Middleware Requirements Next middleware release

gLite 3.1 and other gLite 3.2 products

Support Calendar

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

The products must be retired by 30-09-2012

Operations Calendar


  • 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 decommissioning timeline

Support Calendar

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

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

  • Deployment of unsupported end-points is tracked by the EGI dashboard
  • 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.

EMI 1 decommissioning timeline

Support Calendar

End of security updates and support: 30-04-2013 (http://www.eu-emi.eu/releases#MajRel)

Decommissioning Calendar

EMI 1 products must be decommissioned by 30-04-2013.

  • new probe tested until end of Dec
  • 01-01-2013: monitoring probes start returning WARNING
  • 01-03-2013: monitoring probes start returning CRITICAL

Service end-points which can not be upgraded by this deadline, must be set in downtime as of 01-05-2013, unless upgrading is not possible for technical reasons.

Operations Calendar

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