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 78: Line 78:
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]] should be applied.  
[[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.  


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


|- valign="top"
|- valign="top"

Revision as of 12:20, 3 December 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 Decommissioning of unsupported software
Document link https://wiki.egi.eu/wiki/PROC16
Last modified v1.0 20.11.2012
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations at mailman.egi.eu
Document Status Approved
Approved Date 20.11.2012
Procedure Statement A procedure for removal of unsupported software from production infrastructure.
Owner Owner of procedure


Overview

Unsupported software decommission procedure was created to define steps which have to be taken to remove unsupported software 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.

Decommissioning start date

  • from this day NGIs and sites should start action to move their services to supported software

End of Security Updates and Support

  • from this day the software is unsupported
  • sites should not run unsupported software in production infrastructure

Decommissioning deadline

  • from this day no services with unsupported software can be present in production infrastructure (they should be decommissioned or in downtime)
  • in case of violation COD team can remove the site from production infrastructure


MW campaign.png

Steps



Responsible Action
Decommissioning start date
0 COO
During OMB meeting COO announce End of Security Updates and Support and Decommission deadline for service migration.
1
COO The broadcast is send to NGI operations managers, Site administrators, CSIRT, ROD teams.
2 NGI managers
Propagate the information about migration to their own sites.
3 Nagios team
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.
4 ROD

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

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

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.

Resource centres who fail to provide information about migration plans may risk suspension.

After Decommissioning deadline

5 COD Follow up the migration and if needed suspension of sites which didn't provide information on migration plans and/or failed to put affected service end-points in downtime.


Revision history

Version Authors Date Comments