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
(Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} <br> {{Ops_procedures |Doc_title = Service type retirement Procedure |Doc_link = https://wiki.egi.eu/wiki/PROC16 ...")
 
Line 92: Line 92:
== Note  ==
== Note  ==


<br>
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 <br>ROC <br>ROC_OPERATORS <br>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


*- 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  
After migration deadline
*- a security probe is developed for the security nagios that extracts hostnames from GOCDB associated to type X and raises critical alarm in the security dashboard
# CSIRT team followup the migration and if needed suspend sites which didn't migrate
*- a security probe is developed for the security nagios that extracts hostnames from BDII associated to type X and raises critical alarm in the security dashboard
# if a service specific SU in GGUS exists, the SU should be removed from GGUS  
*probes for the service are removed from profiles <br>ROC <br>ROC_OPERATORS <br>ROC_CRITICAL
# 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 SAM probes at the earliest convenience are removed from the SAM release
# a security probe can be removed (should we do that?)
*documentation about service X should re-classified as obsoleted (I would not remove it from our wiki, but I would just reclassify it)


= Revision history  =
= Revision history  =

Revision as of 13:09, 2 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.

Steps

Step [#]

Resp. Unit

Unit to Contact Procedure Remarks
1
2
3
4
5
6
7
8
9
10

Note

Before migration deadline

  1. OMB announce deadline for service migration + broadcast
  2. NGI managers announce the information to the sites
  3. 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
  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. 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

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

Revision history

Version Authors Date Comments