Difference between revisions of "PROC16 Decommissioning of unsupported software"
Jump to navigation
Jump to search
Line 19: | Line 19: | ||
= Terminology = | = Terminology = | ||
'''Decommissioning start date''' | '''Decommissioning start date''' | ||
*from this date NGIs and sites should start action to move their services to supported versions | *from this date NGIs and sites should start action to move their services to supported versions | ||
'''End of Security Updates and Support''' | '''End of Security Updates and Support''' | ||
*from this day the software is unsupported | *from this day the software is unsupported | ||
Line 33: | Line 33: | ||
*in case of violation security team can remove the site from production infrastructure | *in case of violation security team can remove the site from production infrastructure | ||
<br> | |||
[[Image:MW campaign.png|600px|MW campaign.png]]<br> | |||
= Steps = | |||
Following steps are taken since '''End of Security Updates and Support''' is known for COO | |||
'''Decommissioning start date <br>''' | |||
#COO on OMB announce ''' | #COO on OMB announce'''End of Security Updates and Support '''and '''Decommission deadline''' for service migration. | ||
#The broadcast is send to NGI managers and Site administrators | #The broadcast is send to NGI managers and Site administrators. | ||
#NGI managers announce the information to the | #NGI managers announce the information to the site. | ||
#New probe is developed for the MW nagios that extracts hostnames from GOCDB and BDII associated to type and raises critical alarm in the operations dashboard | #New probe is developed for the MW nagios that extracts hostnames from GOCDB and BDII associated to type and raises critical alarm in the operations dashboard. | ||
#*ROD teams followup the service migration | #*ROD teams 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. | ||
After ''' | After '''Decommisioning deadline''' | ||
#COD team followup the migration and if needed suspend sites which didn't migrate | #COD team followup the migration and if needed suspend sites which didn't migrate or are not in downtime.<br> | ||
== Revision history == | == Revision history == | ||
Line 61: | Line 62: | ||
! Comments | ! Comments | ||
|- | |- | ||
| | | <br> | ||
| | | <br> | ||
| | | <br> | ||
| | | <br> | ||
|} | |} | ||
[[Category:Operations_Procedures]] | [[Category:Operations_Procedures]] |
Revision as of 18:23, 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 date 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
Decommission 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
Steps
Following steps are taken since End of Security Updates and Support is known for COO
Decommissioning start date
- COO on OMB announceEnd of Security Updates and Support and Decommission deadline for service migration.
- The broadcast is send to NGI managers and Site administrators.
- NGI managers announce the information to the site.
- New probe is developed for the MW nagios that extracts hostnames from GOCDB and BDII associated to type and raises critical alarm in the operations dashboard.
- ROD teams 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
- COD team followup the migration and if needed suspend sites which didn't migrate or are not in downtime.
Revision history
Version | Authors | Date | Comments |
---|---|---|---|