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 @ egi.eu.

Difference between revisions of "PROC16 Decommissioning of unsupported software"

From EGIWiki
Jump to navigation Jump to search
Line 71: Line 71:
| 4  
| 4  
| ROD<br>  
| ROD<br>  
| Followup the service migration by creating operations ticket through Operations Dashboard till the '''decommissioning deadline'''. Site admins should provide migration or decommission plan within 2 weeks. If not [[PROC01 Grid Oversight escalation#Escalation_for_operational_problem_with_unsupported_MW_at_site.C2.A0|escalation procedure for problems with unsupported MW at site]] should be applied.
|  
Followup the service migration by creating operations ticket through Operations Dashboard till the '''decommissioning deadline'''.
 
Site admins should provide migration or decommission plan within 2 weeks.
 
If not [[PROC01 Grid Oversight escalation#Escalation_for_operational_problem_with_unsupported_MW_at_site.C2.A0|escalation procedure for problems with unsupported MW at site]] should be applied.
 
|}
|}


Line 89: Line 95:
|}
|}


<br>


== Revision history  ==
== Revision history  ==
Line 104: Line 111:
| <br>
| <br>
|}
|}


[[Category:Operations_Procedures]]
[[Category:Operations_Procedures]]

Revision as of 18:40, 19 November 2012

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators




Title Unsupported software version decommission
Document link https://wiki.egi.eu/wiki/PROC16
Last modified 1.0
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations at mailman.egi.eu
Document Status Draft
Approved Date
Procedure Statement A procedure for removal of unsupported software version from production infrastructure.
Owner Owner of procedure


Overview

Unsupported software version decommission procedure was created to define steps which have to be taken to remove unsupported software version from the production infrastructure.

Terminology

Decommissioning start date

  • from this day NGIs and sites should start action to move their services to supported versions

End of Security Updates and Support

  • from this day the software is unsupported
  • sites should not run unsupported software version in production infrastructure

Decommissioning deadline

  • from this day no services with unsupported software version can be present in production infrastructure (they should be decommissioned or in downtime)
  • in case of violation security team can remove the site from production infrastructure


MW campaign.png

Steps

Following steps are taken since End of Security Updates and Support is known for COO

Decommissioning start date


Responsible Action
0 COO
During OMB meeting COO announce End of Security Updates and Support and Decommission deadline for service migration.
1
COO The broadcast is send to NGI managers and Site administrators.
2 NGI managers
Announce the information about migration to the site.
3 Nagios team
New probe is developed for the MW nagios that extracts hostnames from GOCDB and BDII associated to version and raises critical alarm in the operations dashboard.
4 ROD

Followup the service migration by creating operations ticket through Operations Dashboard till the decommissioning deadline.

Site admins should provide migration or decommission plan within 2 weeks.

If not escalation procedure for problems with unsupported MW at site should be applied.


After Decommisioning deadline


Responsible Action
0 COD
Followup the migration and if needed suspend sites which didn't migrate or are not in downtime.


Revision history

Version Authors Date Comments