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.

PROC17 Decommissioning of service type

From EGIWiki
(Redirected from PROC17)
Jump to navigation Jump to search
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


Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.



Title Decommissioning of service type
Document link https://wiki.egi.eu/wiki/PROC17
Last modified 8 June 2016
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations@egi.eu
Document Status Final
Approved Date 16.07.2013
Procedure Statement A procedure for removal of service type from production infrastructure.
Owner Matthew Viljoen


Overview

The Service type decommission procedure was created to define steps which have to be taken to remove a service type from the production infrastructure.

Definitions

Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Steps

The process starts when the COO opens a GGUS ticket to the Operations SU (via GGUS). Each step which require contact with other teams should be done through GGUS as well (as a child ticket to the main one).

This procedure is run if a software related to the service type is unsupported or it was decided to change the name of the service type.


Responsible Action
1 COO

Decides and announce  decommission deadline for the service type to OMB

Information is send in Operations Monthly broadcast to NGI managers, Site administrators and VO managers by Operations

2 Nagios team A security probe is developed for the security nagios that extracts hostnames from GOCDB and BDII associated to the decommissioned service type and raises critical alarm in the security dashboard
3 Operations
Followup the process until the decommission deadline


After Decommission deadline



Responsible Action
1 SAM team Probes for the service type are removed from profiles:
  • ROC
  • ROC_OPERATORS
  • ROC_CRITICAL
  • the SAM probes at the earliest convenience are removed from the SAM release.
2
GGUS If for the service type specific SU in GGUS exists, the SU should be removed from GGUS.
3 GOCDB The service type should be disabled in GOCDB (i.e. service entries can no more declared to be of the service type), but not removed.
4 Operations
Information about service type decommissioning is send in Operations Monthly broadcast to NGI managers, Site administrators and VO managers by Operations

Revision history

Version Authors Date Comments
1.0 M. Krakowian 19 August 2014 Change from COD to Operations Support team
Alessandro Paolini 2016-06-08 "EGI Operations Support" was decommissioned, changed all the references to "Operations"
Alessandro Paolini 2021-08-13 procedure deprecated since it is superseded by https://confluence.egi.eu/display/EGIPP/PROC16+Decommissioning+of+unsupported+software