The wiki is in the process of being deprecated and migrated to other supports.

PROC17 Decommissioning of service type

From EGIWiki
Revision as of 09:30, 29 April 2013 by Krakow (talk | contribs) (Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} <br> {{Ops_procedures |Doc_title = Service type decommission |Doc_link = https://wiki.egi.eu/wiki/PROC17 |Versio...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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 Service type decommission
Document link https://wiki.egi.eu/wiki/PROC17
Last modified 1.0
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations at mailman.egi.eu
Document Status Draft
Approved Date
Procedure Statement A procedure for removal of service type from production infrastructure.
Owner Owner of procedure


Overview

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

Terminology

Support deadline

  • from this day service type is unsupported
  • sites should not register retired services in production infrastructure
  • NGIs and sites should start action to move their services to supported versions

Decommission deadline

  • from this day no services for the retired service type can be present in production infrastructure
  • in case of violation security team can remove the site from production infrastructure
  • service type is removed from operations tools

Steps

Following steps are taken since support deadline is known for COO

  1. COO on OMB announce decommission deadline for service migration
  2. The broadcast is send to NGi managers and Site administrators
  3. NGI managers announce the information to the sites
  4. Documentation about service X should re-classified as obsoleted (I would not remove it from our wiki, but I would just reclassify it)
  5. Security probe is developed for the security nagios that extracts hostnames from GOCDB and BDII associated to type X and raises critical alarm in the security dashboard
    • ROD teams followup the service migration till the decommission deadline - site admins should provide migration or decommission plan

After Decommision deadline

  1. Probes for the service are removed from profiles:
    • ROC
    • ROC_OPERATORS
    • ROC_CRITICAL
    • the SAM probes at the earliest convenience are removed from the SAM release
  2. CSIRT team followup the migration and if needed suspend sites which didn't migrate
  3. If a service specific SU in GGUS exists, the SU should be removed from GGUS
  4. The service type should be disabled in GOCDB (i.e. service entries can no more declared to be of service type X), but existing instances associated to type X continue to exist
  5. Security probe can be removed (should we do that?)

TODO

  • involve quattor WG

unresponsive sites handling process

  1. NGI will be requested by EGI.eu operations to contact site administrators to provide upgrade plans in the site ticket, DEADLINE MON 12/11
  2. EGI.eu operations will send a VO broadcast warning VO managers about sites risking suspension
  3. In case of no reply from site administrators, the NGI operations management (NGI manager or deputy, security officer) will be requested to put the affected service end-point in downtime, DEADLINE MON 19/11
  4. In case of no action by NGI, EGI CSIRT will suspend the site (after MON 19/11)

I would suggest the following procedure for EGI-CSIRT Security Officer on Duty (SOOD), handling sites that qualified for suspension:

  1. Open ticket in RT ask COO to suspend site X (CCing Site/NGI-Manager, Site/NGI-Security-Contact)
  2. Site/NGI can give a comment here, if we see suddenly some activity from the site we can offer that the site goes immediately in Downtime.
  3. within 24 hours COO gives the green/red light for Suspension in the ticket
  4. After having received an OK from COO, SOOD changes the sites "certification status" to "Suspended"

This is in EGI-CSIRT Critical Vulnerability Operational Procedure: https://documents.egi.eu/secure/RetrieveFile?docid=283&version=9&filename=EGI-CSIRT-Procedure-CriticalSecurity-V8.pdf Skipping the extensive communication part which has for these sites already proven to not work, thus we might want to jump directly to

==

4.5 Carry out Site suspension

Site suspension WILL be carried out by the EGI CSIRT co-ordinator or deputy. Site suspension is carried out by changing the status of the site in the GOCDB to ‘suspended’.

==

Revision history

Version Authors Date Comments