Difference between revisions of "PROC16 Decommissioning of unsupported software"
(→Steps) |
|||
Line 49: | Line 49: | ||
= Steps<br> = | = Steps<br> = | ||
<br>Unsupported software '''MUST | <br>Unsupported software '''MUST be retired no later than 1 month after its End of Security Updates and Support''', with the proviso that after this date, if a critical vulnerability were to emerge, EGI CSIRT can request the service to be turned off immediately. | ||
<br> | <br> |
Revision as of 13:36, 3 December 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 | Decommissioning of unsupported software |
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 from production infrastructure. |
Owner | Owner of procedure |
Overview
Unsupported software decommission procedure was created to define steps which have to be taken to remove unsupported software from the production infrastructure.
Definitions
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Steps
Unsupported software MUST be retired no later than 1 month after its End of Security Updates and Support, with the proviso that after this date, if a critical vulnerability were to emerge, EGI CSIRT can request the service to be turned off immediately.
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 operations managers, Site administrators, CSIRT, ROD teams. |
2 | NGI managers |
Propagate the information about migration to their own sites. |
3 | Nagios team |
New probe is developed for the MW nagios that extracts service end-points from BDII associated to unsupported software and raises critical alarm in the operations dashboard. |
4 | ROD |
Follow up the service migration by creating operations ticket through Operations Dashboard until the decommissioning deadline. Escalation steps for problems with unsupported MW at site must be applied. Site admins must provide migration or decommission plan within 2 weeks. The plan must take into account Decommissioning deadline and site plans to migrate before this date. Resource centres who fail to provide information about migration plans may risk suspension. |
After Decommissioning deadline | ||
5 | COD | Follow up the migration and if needed start putting the affected service end-points in downtime for 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 |
---|---|---|---|