PROC16 Decommissioning of unsupported software
Jump to navigation
Jump to search
Steps
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 | v1.0 20.11.2012 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations at mailman.egi.eu |
Document Status | Approved |
Approved Date | 20.11.2012 |
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
Steps
Responsible | Action | |
---|---|---|
Decommissioning start date | ||
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, Site administrators, CSIRT, ROD teams. |
2 | NGI managers |
Propagate the information about migration to own sites. |
3 | Nagios team |
New probe is developed for the MW nagios that extracts service end-points from BDII associated to unsupported software versions 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 Decommissioning deadline | ||
5 | COD | Followup the migration and if needed suspension of sites which didn't provide information on migration plans and/or failed to put affected service end-points in downtime. |
Revision history
Version | Authors | Date | Comments |
---|---|---|---|