Difference between revisions of "PROC16 Decommissioning of unsupported software"
Jump to navigation
Jump to search
(→Note) |
|||
Line 16: | Line 16: | ||
The Service type retirement Procedure was created to define steps which have to be taken to remove service type from prodcution infrastructure. <br> | The Service type retirement Procedure was created to define steps which have to be taken to remove service type from prodcution infrastructure. <br> | ||
= Terminology = | |||
'''Support deadline''' | |||
*from this day service type is unsupported | |||
*sites '''should not''' register retired services in production infrastructure | |||
*NGIs and sites should start action to move their services to supported versions | |||
'''Retirement deadline''' | |||
*from this day no services for the retired service type can be present in production infrastructure | |||
*in case of violation security team can remove the site from production infrastructure | |||
*service type is removed from operations tools | |||
= Steps = | = Steps = |
Revision as of 17:20, 5 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 | Service type retirement Procedure |
Document link | https://wiki.egi.eu/wiki/PROC16 |
Last modified | 1.0 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operational-documentation@mailman.egi.eu |
Document Status | Draft |
Approved Date | |
Procedure Statement | A procedure for removal of service type from production infrastructure. |
Owner | Owner of procedure |
Overview
The Service type retirement Procedure was created to define steps which have to be taken to remove service type from prodcution infrastructure.
Terminology
Support deadline
- from this day service type is unsupported
- sites should not register retired services in production infrastructure
- NGIs and sites should start action to move their services to supported versions
Retirement deadline
- from this day no services for the retired service type can be present in production infrastructure
- in case of violation security team can remove the site from production infrastructure
- service type is removed from operations tools
Steps
Step [#] |
Resp. Unit |
Unit to Contact | Procedure | Remarks |
1 | ||||
2 | ||||
3 | ||||
4 | ||||
5 | ||||
6 | ||||
7 | ||||
8 | ||||
9 | ||||
10 |
Note
todo: involve quattor WG
Before migration deadline
- OMB announce deadline for service migration + broadcast
- NGI managers announce the information to the sites
- probes for the service are removed from profiles
ROC
ROC_OPERATORS
ROC_CRITICAL and the SAM probes at the earliest convenience are removed from the SAM release - documentation about service X should re-classified as obsoleted (I would not remove it from our wiki, but I would just reclassify it)
- a security probe is developed for the security nagios that extracts hostnames from GOCDB and BDII associated to type X and raises critical alarm in the security dashboard
- ROD teams followup the service migration till the deadline set by OMB - site admins should provide migration or decommision plan
After migration deadline
- CSIRT team followup the migration and if needed suspend sites which didn't migrate
- if a service specific SU in GGUS exists, the SU should be removed from GGUS
- the service type should be disabled in GOCDB (i.e. service entries can no more declared to be of service type X), but existing instances associated to type X continue to exist
- a security probe can be removed (should we do that?)
Revision history
Version | Authors | Date | Comments |
---|---|---|---|