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"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
= Overview = | = Overview = | ||
The Service type decommission procedure was created to define steps which have to be taken to remove service type from prodcution infrastructure. <br> | The Service type decommission procedure was created to define steps which have to be taken to remove service type from prodcution infrastructure. <br> | ||
= Terminology = | = Terminology = | ||
'''Support deadline''' | '''Support deadline''' | ||
*from this day service type is unsupported | |||
*from this day service type is unsupported | |||
*sites '''should not''' register retired services in production infrastructure | *sites '''should not''' register retired services in production infrastructure | ||
*NGIs and sites should start action to move their services to supported versions | *NGIs and sites should start action to move their services to supported versions | ||
'''Decommission deadline''' | '''Decommission 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 | *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 | *service type is removed from operations tools | ||
= Steps = | = Steps = | ||
Following steps are taken since '''support deadline''' is known for COO | Following steps are taken since '''support deadline''' is known for COO | ||
#COO on OMB announce '''decommission deadline''' for service migration | |||
#The broadcast is send to NGI managers and Site administrators | |||
#NGI managers announce the information to the sites | |||
#Documentation about decommissioned service should re-classified as obsoleted (I would not remove it from our wiki, but I would just reclassify it) | |||
#New probe is developed for the MW nagios that extracts hostnames from GOCDB and BDII associated to type and raises critical alarm in the operations dashboard | |||
#* ROD teams followup the service migration till the decommission deadline - site admins should provide migration or decommission plan See instruction | |||
After '''Decommision deadline''' | |||
#Probes for the service are removed from profiles: | |||
# Probes for the service are removed from profiles: | #*ROC | ||
#*ROC | |||
#*ROC_OPERATORS | #*ROC_OPERATORS | ||
#*ROC_CRITICAL | #*ROC_CRITICAL | ||
#*the SAM probes at the earliest convenience are removed from the SAM release | #*the SAM probes at the earliest convenience are removed from the SAM release | ||
# CSIRT team followup the migration and if needed suspend sites which didn't migrate | #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 | #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 | #The service type should be disabled in GOCDB (i.e. service entries can no more declared to be of the service type), but existing instances associated to the type continue to exist<br> | ||
== Instuctions for ROD teams == | |||
= Revision history = | = Revision history = | ||
Revision as of 12:49, 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 | Service type 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 service type from production infrastructure. |
| Owner | Owner of procedure |
Overview
The Service type decommission 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
Decommission 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
Following steps are taken since support deadline is known for COO
- COO on OMB announce decommission deadline for service migration
- The broadcast is send to NGI managers and Site administrators
- NGI managers announce the information to the sites
- Documentation about decommissioned service should re-classified as obsoleted (I would not remove it from our wiki, but I would just reclassify it)
- New probe is developed for the MW nagios that extracts hostnames from GOCDB and BDII associated to type and raises critical alarm in the operations dashboard
- ROD teams followup the service migration till the decommission deadline - site admins should provide migration or decommission plan See instruction
After Decommision deadline
- Probes for the service are removed from profiles:
- ROC
- ROC_OPERATORS
- ROC_CRITICAL
- the SAM probes at the earliest convenience are removed from the SAM release
- 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 the service type), but existing instances associated to the type continue to exist
Instuctions for ROD teams
Revision history
| Version | Authors | Date | Comments |
|---|---|---|---|