Closed Bug 1646823 Opened 6 years ago Closed 6 years ago

Decomm unused relabs VMs

Categories

(Infrastructure & Operations :: Virtualization, task)

Product:
Infrastructure & Operations
Component:
Virtualization
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dividehex, Assigned: cknowles)

References

Details

(Whiteboard: [vm-delete:5])

Current list of VMs to decomm:
relabs-puppet1.relabs.releng.mdc1.mozilla.com
relabs-test1.relabs.releng.mdc1.mozilla.com
bsdpy1.relabs.releng.mdc2.mozilla.com
relabs-puppet1.relabs.releng.mdc2.mozilla.com
relabs-test1.relabs.releng.mdc2.mozilla.com

relabs-puppet1.relabs.releng.mdc1.mozilla.com - 10.49.78.100
relabs-test1.relabs.releng.mdc1.mozilla.com - 10.49.78.24
bsdpy1.relabs.releng.mdc2.mozilla.com - 10.51.78.44
relabs-puppet1.relabs.releng.mdc2.mozilla.com - 10.51.78.100
relabs-test1.relabs.releng.mdc2.mozilla.com - 10.51.78.24

I see all of them as down, and no entries in proxy (being in releng) and nothing in nagios. Will now pause for a bit to make sure there's no screaming.

Assignee: server-ops-virtualization → cknowles

Removed from Inventory
Removed from DNS
Removed from tracking
Removed from vCenter

These have been cleaned up. Thanks!

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Whiteboard: [vm-delete:5]

Jira issue "NETOPS-1995" has been issued to clean up the firewall rules associated with the relabs-puppet1 VMs.

You need to log in before you can comment on or make changes to this bug.