Page MenuHomePhabricator

Decommission dbproxy1005.eqiad.wmnet
Open, NormalPublic


This task will track the decommission of server dbproxy1005.eqiad.wmnet

The first 5 steps should be completed by the service owner that is returning the server to DC-ops (for reclaim to spare or decommissioning, dependent on server configuration and age.)

Steps for service owner:

  • - all system services confirmed offline from production use
  • - set all icinga checks to maint mode/disabled while reclaim/decommmission takes place.
  • - remove system from all lvs/pybal active configuration
  • - any service group puppet/hiera/dsh config removed
  • - remove site.pp, replace with role(spare::system)
  • - unassign service owner from this task, check off completed steps, and assign to @RobH for followup on below steps.

Steps for DC-Ops:

The following steps cannot be interrupted, as it will leave the system in an unfinished state.

Start non-interrupt steps:

  • - disable puppet on host
  • - power down host
  • - update netbox status to Inventory (if decom) or Planned (if spare)
  • - disable switch port
  • - switch port assignment noted on this task (for later removal)
  • - remove all remaining puppet references (include role::spare)
  • - remove production dns entries
  • - puppet node clean, puppet node deactivate (handled by wmf-decommission-host)
  • - remove dbmonitor entries on neodymium/sarin: sudo curl -X DELETE https://debmonitor.discovery.wmnet/hosts/${HOST_FQDN} --cert /etc/debmonitor/ssl/cert.pem --key /etc/debmonitor/ssl/server.key (handled by wmf-decommission-host)

End non-interrupt steps.

  • - system disks wiped (by onsite)
  • - IF DECOM: system unracked and decommissioned (by onsite), update racktables with result
  • - IF DECOM: switch port configration removed from switch once system is unracked.
  • - IF DECOM: add system to decommission tracking google sheet
  • - IF DECOM: mgmt dns entries removed.
  • - IF RECLAIM: system added back to spares tracking (by onsite)

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptWed, Sep 4, 7:58 AM
Marostegui triaged this task as Normal priority.Wed, Sep 4, 7:59 AM
Marostegui moved this task from Triage to In progress on the DBA board.

Nothing uses dbproxy1005, but I am going to stop haproxy and leave it stopped for some hours before fully decommissioning this host just in case.

Change 534298 had a related patch set uploaded (by Marostegui; owner: Marostegui):
[operations/puppet@production] dbproxy1005: Disable notifications

Change 534298 merged by Marostegui:
[operations/puppet@production] dbproxy1005: Disable notifications

Mentioned in SAL (#wikimedia-operations) [2019-09-04T08:42:09Z] <marostegui> Stop HAproxy on dbproxy1005 - T231967

Marostegui updated the task description. (Show Details)Thu, Sep 5, 5:10 AM
Marostegui updated the task description. (Show Details)Thu, Sep 5, 6:03 AM

Change 534563 had a related patch set uploaded (by Marostegui; owner: Marostegui):
[operations/puppet@production] mariadb: Decommission dbproxy1005

Change 534563 merged by Marostegui:
[operations/puppet@production] mariadb: Decommission dbproxy1005

Marostegui reassigned this task from Marostegui to RobH.Thu, Sep 5, 6:39 AM
Marostegui updated the task description. (Show Details)
Marostegui edited projects, added decommission, ops-eqiad; removed Patch-For-Review, DBA.
Marostegui updated the task description. (Show Details)
Marostegui added a project: DC-Ops.

This host is ready for DC-Ops to get it decommissioned