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.

PROC16 Decommissioning of unsupported software

From EGIWiki
Revision as of 15:58, 20 November 2012 by Krakow (talk | contribs)
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




Title Unsupported software version decommission
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 version from production infrastructure.
Owner Owner of procedure


Overview

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

End of Security Updates and Support

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

Decommissioning deadline

  • from this day no services with unsupported software version 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 managers, Site administrators, CSIRT, ROD teams.
2 NGI managers
 Propagate the information about migration to own sites.
3 Nagios team
 New probe is developed for the MW nagios that extracts service end-points from BDII associated to unsupported software versions and raises critical alarm in the operations dashboard.
4 ROD

Followup the service migration by creating operations ticket through Operations Dashboard till the decommissioning deadline.

Site admins should provide migration or decommission plan within 2 weeks.

If not escalation procedure for problems with unsupported MW at site should be applied.

After Decommissioning deadline

5 COD Followup 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




Retrieved from "https://wiki.egi.eu/w/index.php?title=PROC16_Decommissioning_of_unsupported_software&oldid=45772"