Closed Bug 1310984 Opened 8 years ago Closed 8 years ago

Decommission VM: selenium-hub-staging1.qa.scl3.mozilla.com

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

Product:
Infrastructure & Operations
Component:
MOC: Service Requests
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: davehunt, Assigned: sal)

Details

(Keywords: spring-cleaning, Whiteboard: [vm-delete:1]) 

We are no longer using Selenium Grid, and are therefore shutting down this infrastructure. Please decommission selenium-hub-staging1.qa.scl3.mozilla.com (created via bug 1186861). Note that there should not be any monitoring running for the services running on this box.
Assignee: server-ops-virtualization → nobody
Component: Virtualization → MOC: Service Requests
QA Contact: cshields → lypulong
Keywords: spring-cleaning
Assignee: nobody → sespinoza
Status: NEW → ASSIGNED
selenium-hub-staging1.qa.scl3.mozilla.com has address 10.22.73.158

-Removed from nagios 
-Host powered down
Thanks :sal, is there a reason this is still open?
Flags: needinfo?(sespinoza)
Yes, there's a whole checklist of things that have to happen to decomm a host - removing from monitoring, disabling puppet and powering it down is phase 1 - basically the "easy to reverse" items - then there's a pause of "a week-ish, in case there's an unrealized dependency" and then phase 2, where we delete the VM, and delete records related to it, and then it's *REALLY* gone.
Flags: needinfo?(sespinoza)
Thanks for clarifying. :)
:cknowles, :gcox please nuke this one? ...oh and thanks for clearing my NI cknowles!

-Filed Bug 1313514 for netops
-Removed DNS 
-Removed from foreman
Deleted as requested.
Whiteboard: [vm-delete:1]
closing.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.