Difference between revisions of "PROC16 Decommissioning of unsupported software"
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
'''Decommission deadline''' | '''Decommission deadline''' | ||
*from this day '''no services | *from this day '''no services with unsupported software version can be present in production infrastructure''' | ||
*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 | ||
= Steps = | = Steps = |
Revision as of 16:39, 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 prodcution infrastructure.
Terminology
Support deadline
- from this day the software is unsupported
- sites should not run unsupported software version in production infrastructure
- NGIs and sites should start action to move their services to supported versions
Decommission deadline
- from this day no services with unsupported software version can be present in production infrastructure
- in case of violation security team can remove the site from production infrastructure
Steps
Following steps are taken since support deadline is known for COO
- COO on OMB announce decommission deadline for service migration
- The broadcast is send to NGI managers and Site administrators
- NGI managers announce the information to the sites
- 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 procedure till the decommission deadline - site admins should provide migration or decommission plan. See escalation procedure
After Decommision deadline
- COD team followup the migration and if needed suspend sites which didn't migrate
Revision history
Version | Authors | Date | Comments |
---|---|---|---|