Page tree
Skip to end of metadata
Go to start of metadata

Document control

AreaEGI Federation Operations
Procedure status

FINAL

OwnerAlessandro Paolini 
ApproversOperations Management Board
Approval status

APPROVED

Approved version and date

v8,  

Statement

A procedure for removal of unsupported software from production infrastructure

Next procedure reviewon demand

Procedure reviews

The following table is updated after every review of this procedure.

DateReview bySummary of resultsFollow-up actions / Comments

 

Alessandro Paolini copy from PROC16_Decommissioning_of_unsupported_software in EGI Wiki




Table of contents

Overview

Unsupported software decommission procedure was created to define steps which have to be taken to remove unsupported software from the production infrastructure.

Policy

In compliance to the EGI Service Operations Security Policy (1), unsupported software SHOULD be decommissioned before its End of Security Updates and Support, and MUST be retired no later than 1 month after its End of Security Updates and Support. After this date, if a critical vulnerability were to emerge in the software, EGI CSIRT can request the service to be turned off immediately.

(1) a Resource Centre Administrator SHOULD follow IT security best practices that include pro-actively applying software patches, updates or configuration changes related to security.

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.

Timelines

Decommissioning start date

By this date NGIs and sites SHOULD start action to upgrade their services to supported software or retire them.

End of Security Updates and Support

By this date the software is unsupported. Resource Centres SHOULD NOT run unsupported software in their production infrastructure.

Decommissioning deadline

By this date unsupported software MUST BE retired from the production infrastructure (they must be decommissioned or in downtime). Failure to do so MAY ultimately lead to site suspension or the affected service-end points to be put in downtime by ROD/Operations Support teams. This is applicable to Resource Centres that do not respond to tickets, or for which no technical issue exists preventing them from retiring unsupported software. Status of Resource Centres will be examined by ROD/Operations Support on a case by case.

Entities involved in the procedure

  • EGI Operations
  • NGIs Managers
  • ARGO Monitoring team
  • ROD teams
  • Site-administrators

Triggers

A product team announces the end of support of a middleware stack

Steps

Preparation phase


ResponsibleAction
0EGI Operations During an OMB meeting the Operations announces End of Security Updates and Support and Decommission deadline for service migration.
1EGI Operations

Information is sent in Monthly broadcast to NGI operations managers, Site administrators, CSIRT, ROD teams:

  • service type decommissioned or product reaching end of life
  • date of the end of support
  • date of starting the campaign
  • date of ending the campaign
  • link to the procedure applied
2NGI managersPropagate the information about migration to their own sites.
3ARGO Monitoring teamA new probe is developed for deploying in the monitoring system. It extracts information about deployed software versions from Information discovery service (e.g. BDII).

Escalation phase


TimelineResponsibleAction
1

Decommissioning

start date

ARGO Monitoring teamNew probe is deployed into the monitoring system and starts returning WARNING.
2

Decommissioning

start date + 1 month

ARGO Monitoring teamThe probe starts returning CRITICAL.
ROD

Follow up the service migration by creating operations ticket through Operations Dashboard until the decommissioning deadline.

Escalation steps for problems with unsupported Middleware at site must be applied.

3

within 10 working days

from when ROD ticket is received

Site admins

Site admins must provide migration or decommission plan within 10 working days from when ROD ticket is received.

The plan must take into account Decommissioning deadline and site plans to migrate before this date.

Resource centres who fail to provide information about migration plans are subject to suspension by ROD.

4

After10 working days
ROD

Follow up the migration:

  • sites which didn't provide information on migration plans can be suspended
5Decommissioning deadlineROD and Site admins

By this time service end-points which couldn't be upgraded should be put into downtime by site admin or ROD:

  • Type: Scheduled
  • Severity: Warning
6After Decommissioning deadlineOperationsFollow up the status of migration and put in downtime affected end-points.
7Decommissioning deadline + 1 monthOperationsSites still deploying unsupported service end-points risk suspension, unless documented technical reasons prevent a Site Admin from updating these end-points.