Alert.png 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"

From EGIWiki
Jump to navigation Jump to search
Line 34: Line 34:


# COO on OMB announce '''decommission deadline''' for service migration  
# COO on OMB announce '''decommission deadline''' for service migration  
# the broadcast is send to NGi managers and Site administrators
# The broadcast is send to NGi managers and Site administrators
# NGI managers announce the information to the sites
# NGI managers announce the information to the sites
# documentation about service X should re-classified as obsoleted (I would not remove it from our wiki, but I would just reclassify it)
# 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  
# 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 decommission deadline - site admins should provide migration or decommission plan
#* ROD teams followup the service migration till the decommission deadline - site admins should provide migration or decommission plan


After '''Decommision deadline'''
After '''Decommision deadline'''
# probes for the service are removed from profiles <br>ROC <br>ROC_OPERATORS <br>ROC_CRITICAL and the SAM probes at the earliest convenience are removed from the SAM release  
# 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  
# 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 X), but existing instances associated to type X continue to exist  
# 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?)
# Security probe can be removed (should we do that?)


== TODO ==
== TODO ==


* involve quattor WG  
* involve quattor WG
 


= Revision history  =
= Revision history  =

Revision as of 17:36, 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 decommision 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 decomission 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

  1. COO on OMB announce decommission deadline for service migration
  2. The broadcast is send to NGi managers and Site administrators
  3. NGI managers announce the information to the sites
  4. Documentation about service X should re-classified as obsoleted (I would not remove it from our wiki, but I would just reclassify it)
  5. 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 decommission deadline - site admins should provide migration or decommission plan

After Decommision deadline

  1. 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
  2. CSIRT team followup the migration and if needed suspend sites which didn't migrate
  3. If a service specific SU in GGUS exists, the SU should be removed from GGUS
  4. 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
  5. Security probe can be removed (should we do that?)

TODO

  • involve quattor WG

Revision history

Version Authors Date Comments
Retrieved from "https://wiki.egi.eu/w/index.php?title=PROC16_Decommissioning_of_unsupported_software&oldid=44724"