Difference between revisions of "PROC16 Decommissioning of unsupported software"
Jump to navigation
Jump to search
Line 45: | Line 45: | ||
Following steps are taken since '''End of Security Updates and Support''' is known for COO | Following steps are taken since '''End of Security Updates and Support''' is known for COO | ||
''' | '''<br>''' | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 52: | Line 52: | ||
! Responsible | ! Responsible | ||
! Action | ! Action | ||
|- valign="top" | |||
| colspan="3" | '''Decommissioning start date''' | |||
|- valign="top" | |- valign="top" | ||
| 0 | | 0 | ||
Line 78: | Line 80: | ||
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. | 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. | ||
| | |- valign="top" | ||
| colspan="3" | | |||
After '''Decommisioning deadline''' | |||
|- valign="top" | |- valign="top" | ||
| | | 5 | ||
| COD | | COD | ||
| Followup the migration and if needed suspend sites which didn't migrate or are not in downtime. | | Followup the migration and if needed suspend sites which didn't migrate or are not in downtime. | ||
|} | |} |
Revision as of 18:43, 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
Steps
Following steps are taken since End of Security Updates and Support is known for COO
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 and Site administrators. |
2 | NGI managers |
Propagate the information about migration to own sites. |
3 | Nagios team |
New probe is developed for the MW nagios that extracts hostnames from GOCDB and BDII associated to version 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 Decommisioning deadline | ||
5 | COD | Followup the migration and if needed suspend sites which didn't migrate or are not in downtime. |
Revision history
Version | Authors | Date | Comments |
---|---|---|---|