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"
(→Steps) |
|||
| Line 56: | Line 56: | ||
|- | |- | ||
! <br> | ! <br> | ||
! Timeline | |||
! Responsible | ! Responsible | ||
! Action | ! Action | ||
|- valign="top" | |- valign="top" | ||
| 0 | | 0 | ||
| (without delay) | |||
| COO<br> | | COO<br> | ||
| During an OMB meeting the COO announces '''End of Security Updates and Support '''and '''Decommission deadline''' for service migration. | | During an OMB meeting the COO announces '''End of Security Updates and Support '''and '''Decommission deadline''' for service migration. | ||
|- valign="top" | |- valign="top" | ||
| 1<br> | | 1<br> | ||
| (without delay) | |||
| COO | | COO | ||
| The broadcast is send to NGI operations managers, Site administrators, CSIRT, ROD teams. | | The broadcast is send to NGI operations managers, Site administrators, CSIRT, ROD teams. | ||
|- valign="top" | |- valign="top" | ||
| 2 | | 2 | ||
| (without delay) | |||
| NGI managers<br> | | NGI managers<br> | ||
| Propagate the information about migration to their own sites. | | Propagate the information about migration to their own sites. | ||
|- valign="top" | |- valign="top" | ||
| 3 | | 3 | ||
| (without delay) | |||
| Nagios team<br> | | Nagios team<br> | ||
| 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. | | 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. | ||
|- valign="top" | |- valign="top" | ||
| 4 | | 4 | ||
| | |||
'''Decommissioning '''<br> | |||
'''start date''' | |||
| Nagios team | |||
| Put new probe into the MW nagios. | |||
|- valign="top" | |||
| 5 | |||
| (without delay) | |||
| ROD<br> | | ROD<br> | ||
| | | | ||
| Line 89: | Line 102: | ||
|- valign="top" | |- valign="top" | ||
| | |||
6 | |||
| | |||
'''Decommissioning '''<br> | |||
'''start date + 2 weeks<br>''' | |||
| ROD | |||
| 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. | |||
|- valign="top" | |- valign="top" | ||
| | | 7 | ||
| After '''Decommissioning deadline''' | |||
| COD | | COD | ||
| Follow up the migration and if needed | | Follow up the migration and if needed suspend sites which didn't provide information on migration plans and/or failed to put affected service end-points in downtime. | ||
|} | |} | ||
Revision as of 11:40, 4 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.
|
Decommissioning start date
End of Security Updates and Support
Decommissioning deadline
|
|
Steps
Unsupported software MUST be retired no later than 1 month after its End of Security Updates and Support. After this date, if a critical vulnerability were to emerge in the software, EGI CSIRT can request the service to be turned off immediately
| Timeline | Responsible | Action | |
|---|---|---|---|
| 0 | (without delay) | COO |
During an OMB meeting the COO announces End of Security Updates and Support and Decommission deadline for service migration. |
| 1 |
(without delay) | COO | The broadcast is send to NGI operations managers, Site administrators, CSIRT, ROD teams. |
| 2 | (without delay) | NGI managers |
Propagate the information about migration to their own sites. |
| 3 | (without delay) | 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 |
Decommissioning start date |
Nagios team | Put new probe into the MW nagios. |
| 5 | (without delay) | 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 from Decomissioning start date. 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 are subject to suspension. |
|
6 |
Decommissioning start date + 2 weeks |
ROD | 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. |
| 7 | After Decommissioning deadline | COD | Follow up the migration and if needed suspend 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 |
|---|---|---|---|