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
(43 intermediate revisions by 4 users not shown)
Line 4: Line 4:
|Doc_title = Decommissioning of unsupported software
|Doc_title = Decommissioning of unsupported software
|Doc_link = [[PROC16|https://wiki.egi.eu/wiki/PROC16]]
|Doc_link = [[PROC16|https://wiki.egi.eu/wiki/PROC16]]
|Version = v1.0 20.11.2012
|Version = 8 June 2016
|Policy_acronym = OMB
|Policy_acronym = OMB
|Policy_name = Operations Management Board
|Policy_name = Operations Management Board
|Contact_group = operations at mailman.egi.eu
|Contact_group = operations@egi.eu
|Doc_status = Approved
|Doc_status = Approved
|Approval_date = 20.11.2012
|Approval_date = 20.11.2012
|Procedure_statement = A procedure for removal of unsupported software from production infrastructure.  
|Procedure_statement = A procedure for removal of unsupported software from production infrastructure.  
|Owner = Vincenzo Spinoso
}}  
}}  


Line 17: Line 18:
Unsupported software decommission procedure was created to define steps which have to be taken to remove unsupported software from the production infrastructure.  
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 (https://documents.egi.eu/public/ShowDocument?docid=1475) (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  =
= Definitions  =


  Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.  
Please refer to the [[Glossary|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.  
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.  


{|
== 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. <!--{|
|-
|-
|  
|  
Line 39: Line 54:
'''Decommissioning deadline'''  
'''Decommissioning deadline'''  


*from this day '''no services with unsupported software can be present in production infrastructure''' (they should be decommissioned or in downtime)  
*from this day '''no services with unsupported software can be present in production infrastructure''' (they must be decommissioned or in downtime)  
*in case of violation COD team can remove the site from production infrastructure by suspension or by putting affected service end-points into downtime<br>
*in case of violation COD team can remove the site from production infrastructure by suspension or by putting affected service end-points into downtime<br>


Line 46: Line 61:
| [[Image:MW campaign.png|600px|MW campaign.png]]
| [[Image:MW campaign.png|600px|MW campaign.png]]
|}
|}
--> [[Image:MW campaign.png|600px|MW campaign.png]]


= Steps<br>  =
= Steps<br>  =


<br>Unsupported software '''MUST''''''be retired no later than 1 month after its End of''''''Security Updates and Support''', with the proviso that after this date, if a critical vulnerability were to emerge, EGI CSIRT can request the service to be turned off immediately.
== Preparation phase  ==
 
<br>


{| class="wikitable"
{| class="wikitable"
Line 58: Line 72:
! Responsible  
! Responsible  
! Action
! Action
|- valign="top"
| colspan="3" | '''Decommissioning start date'''
|- valign="top"
|- valign="top"
| 0  
| 0  
| COO<br>
| EGI&nbsp;Operations&nbsp;
| During OMB meeting COO&nbsp;announce '''End of Security Updates and Support '''and '''Decommission deadline''' for service migration.
| During an OMB meeting the Operations announces '''End of Security Updates and Support '''and '''Decommission deadline''' for service migration.
|- valign="top"
|- valign="top"
| 1<br>  
| 1<br>  
| COO
| EGI Operations
| The broadcast is send to NGI operations managers, Site administrators, CSIRT, ROD teams.
|  
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
 
|- valign="top"
|- valign="top"
| 2  
| 2  
Line 75: Line 95:
| 3  
| 3  
| Nagios team<br>  
| Nagios team<br>  
| New probe is developed for the MW nagios that extracts service end-points from BDII associated to unsupported software and raises critical alarm in the operations dashboard.
| A new probe is developed for the MW SAM for deployment. It extracts information about deployed software versions from Information discovery service (e.g. BDII).<br>
|}
 
<br>
 
== Escalation phase  ==
 
{| class="wikitable"
|-
! <br>
! Timeline
! Responsible
! Action
|- valign="top"
| 1
|
'''Decommissioning '''<br>
 
'''start date'''
 
| Nagios team
| New probe is deployed into the MW SAM and starts returning WARNING.
|- valign="top"
| rowspan="2" | 2 <br> <br>
| rowspan="2" | <br> <br>
'''Decommissioning '''<br>
 
'''start date + 1 month'''
 
| Nagios team
| The probe starts returning CRITICAL.
|- valign="top"
|- valign="top"
| 4
| ROD<br>  
| ROD<br>  
|  
|  
Follow up the service migration by creating operations ticket through Operations Dashboard until the '''decommissioning deadline'''.  
Follow up the service migration by creating operations ticket through Operations Dashboard until the '''decommissioning deadline'''.  


[[PROC01 Grid Oversight escalation#Escalation_for_operational_problem_with_unsupported_MW_at_site.C2.A0|Escalation steps for problems with unsupported MW at site]] must be applied.  
[[PROC01 Grid Oversight escalation#Escalation_for_operational_problem_with_unsupported_MW_at_site.C2.A0|Escalation steps for problems with unsupported Middleware at site]] must be applied.  
 
|- valign="top"
| 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.'''


'''Site admins must provide migration or decommission plan within 2 weeks.''' The plan must take into account Decommissioning deadline and site plans to migrate before this date.  
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 may risk suspension.  
Resource centres who fail to provide information about migration plans are subject to suspension by ROD.  


|- valign="top"
|- valign="top"
| colspan="3" |  
|  
After '''Decommissioning deadline'''  
4
 
| '''After10 working days<br>'''  
| ROD
|
Follow up the migration:
 
*sites which didn't provide information on migration plans can be suspended<br>


|- valign="top"
|- valign="top"
| 5  
| 5  
| COD
| '''Decommissioning deadline'''
| Follow up the migration and if needed start putting the affected service end-points in downtime for sites which didn't provide information on migration plans and/or failed to put affected service end-points in downtime.
| ROD 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
 
|- valign="top"
| 6
| '''After Decommissioning deadline '''
| Operations
| Follow up the status of migration and put in downtime affected end-points.
|- valign="top"
| 7
| '''Decommissioning deadline + 1 month'''
| Operations
| Sites still deploying unsupported service end-points risk suspension, unless documented technical reasons prevent a Site Admin from updating these end-points.
|}
|}


Line 110: Line 193:
|-
|-
| <br>  
| <br>  
| <br>
| M. Krakowian
| <br>
| 19 August 2014
| <br>
| Change from COD to Operations Support team
|-
|
| Alessandro Paolini
| 2016-06-08
| "EGI Operations Support" was decommissioned, changed all the references to "Operations"
|}
|}


[[Category:Operations_Procedures]]
[[Category:Operations_Procedures]]

Revision as of 16:37, 7 January 2019

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 Decommissioning of unsupported software
Document link https://wiki.egi.eu/wiki/PROC16
Last modified 8 June 2016
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations@egi.eu
Document Status Approved
Approved Date 20.11.2012
Procedure Statement A procedure for removal of unsupported software from production infrastructure.
Owner Vincenzo Spinoso


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 (https://documents.egi.eu/public/ShowDocument?docid=1475) (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.

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. MW campaign.png

Steps

Preparation phase


 Responsible Action
0 EGI Operations  During an OMB meeting the Operations announces End of Security Updates and Support and Decommission deadline for service migration.
1
 EGI 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
2 NGI managers
 Propagate the information about migration to their own sites.
3 Nagios team
 A new probe is developed for the MW SAM for deployment. It extracts information about deployed software versions from Information discovery service (e.g. BDII).


Escalation phase


 Timeline Responsible Action
1

Decommissioning

start date

Nagios team New probe is deployed into the MW SAM and starts returning WARNING.
2



Decommissioning

start date + 1 month

Nagios team The 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
5 Decommissioning deadline ROD 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
6 After Decommissioning deadline Operations Follow up the status of migration and put in downtime affected end-points.
7 Decommissioning deadline + 1 month Operations Sites still deploying unsupported service end-points risk suspension, unless documented technical reasons prevent a Site Admin from updating these end-points.


Revision history

Version Authors Date Comments

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"
Retrieved from "https://wiki.egi.eu/w/index.php?title=PROC16_Decommissioning_of_unsupported_software&oldid=100850"