Closed Bug 1219260 Opened 9 years ago Closed 9 years ago

please decommission panda infrastructure

Categories

(Infrastructure & Operations :: DCOps, task)

Product:
Infrastructure & Operations
Component:
DCOps
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: arich, Unassigned)

References

Details

We're decommissioning another large chunk of the panda infrastructure. Please decommission the following hardware and dispose of it (associated pandas in parens after the parent relay). They have already been removed from nagios. from rack p3: panda-relay-023.p3.releng.scl3.mozilla.com (258-268) panda-relay-024.p3.releng.scl3.mozilla.com (269-279) panda-relay-025.p3.releng.scl3.mozilla.com (280-290) panda-relay-026.p3.releng.scl3.mozilla.com (291-301, 620) panda-chassis-023.p3.releng.scl3.mozilla.com panda-chassis-024.p3.releng.scl3.mozilla.com panda-chassis-025.p3.releng.scl3.mozilla.com panda-chassis-026.p3.releng.scl3.mozilla.com from rack p10: panda-relay-002.p10.releng.scl3.mozilla.com (22-32) panda-relay-003.p10.releng.scl3.mozilla.com (34-43) panda-relay-004.p10.releng.scl3.mozilla.com (46-55) panda-chassis-002.p10.releng.scl3.mozilla.com panda-chassis-003.p10.releng.scl3.mozilla.com panda-chassis-004.p10.releng.scl3.mozilla.com Everything in rack p1: https://inventory.mozilla.org/en-US/systems/racks/?rack=367 panda-relay-007.p1.releng.scl3.mozilla.com (82-92, 610) panda-relay-008.p1.releng.scl3.mozilla.com (93-103, 611) panda-relay-009.p1.releng.scl3.mozilla.com (104-114, 612) panda-relay-010.p1.releng.scl3.mozilla.com (115-125) panda-relay-011.p1.releng.scl3.mozilla.com (127-136, 613-614) panda-relay-012.p1.releng.scl3.mozilla.com (137-147) panda-relay-013.p1.releng.scl3.mozilla.com (148-158, 615) panda-relay-014.p1.releng.scl3.mozilla.com (159-169) panda-chassis-007.p1.releng.scl3.mozilla.com panda-chassis-008.p1.releng.scl3.mozilla.com panda-chassis-009.p1.releng.scl3.mozilla.com panda-chassis-010.p1.releng.scl3.mozilla.com panda-chassis-011.p1.releng.scl3.mozilla.com panda-chassis-012.p1.releng.scl3.mozilla.com panda-chassis-013.p1.releng.scl3.mozilla.com panda-chassis-014.p1.releng.scl3.mozilla.com mobile-imaging-001.p1.releng.scl3.mozilla.com foopy39.p1.releng.scl3.mozilla.com foopy40.p1.releng.scl3.mozilla.com foopy41.p1.releng.scl3.mozilla.com foopy42.p1.releng.scl3.mozilla.com foopy43.p1.releng.scl3.mozilla.com foopy44.p1.releng.scl3.mozilla.com foopy45.p1.releng.scl3.mozilla.com Everything in rack p2: https://inventory.mozilla.org/en-US/systems/racks/?rack=368 panda-relay-015.p2.releng.scl3.mozilla.com (170-180) panda-relay-016.p2.releng.scl3.mozilla.com (181-191, 616) panda-relay-017.p2.releng.scl3.mozilla.com (192-202) panda-relay-018.p2.releng.scl3.mozilla.com (203-212) panda-relay-019.p2.releng.scl3.mozilla.com (214-224,617) panda-relay-020.p2.releng.scl3.mozilla.com (225-235, 618) panda-relay-021.p2.releng.scl3.mozilla.com (236-246) panda-relay-022.p2.releng.scl3.mozilla.com (33, 247-255) panda-chassis-015.p2.releng.scl3.mozilla.com panda-chassis-016.p2.releng.scl3.mozilla.com panda-chassis-017.p2.releng.scl3.mozilla.com panda-chassis-018.p2.releng.scl3.mozilla.com panda-chassis-019.p2.releng.scl3.mozilla.com panda-chassis-020.p2.releng.scl3.mozilla.com panda-chassis-021.p2.releng.scl3.mozilla.com panda-chassis-022.p2.releng.scl3.mozilla.com mobile-imaging-002.p2.releng.scl3.mozilla.com foopy46.p2.releng.scl3.mozilla.com foopy47.p2.releng.scl3.mozilla.com foopy48.p2.releng.scl3.mozilla.com foopy49.p2.releng.scl3.mozilla.com foopy50.p2.releng.scl3.mozilla.com foopy51.p2.releng.scl3.mozilla.com foopy52.p2.releng.scl3.mozilla.com
foopies and pandas powered off, burn out period starting.
colo-trip: --- → scl3
QA Contact: jbarnell
We've added another chunk of machines to decommission: The rest of p3: https://inventory.mozilla.org/en-US/systems/racks/?rack=365 mobile-imaging-003.p3.releng.scl3.mozilla.com panda-relay-027.p3.releng.scl3.mozilla.com (303-312) panda-relay-028.p3.releng.scl3.mozilla.com (313-323) panda-relay-029.p3.releng.scl3.mozilla.com (324-334) panda-relay-030.p3.releng.scl3.mozilla.com (335-343, 624-625) panda-chassis-027.p3.releng.scl3.mozilla.com panda-chassis-028.p3.releng.scl3.mozilla.com panda-chassis-029.p3.releng.scl3.mozilla.com panda-chassis-030.p3.releng.scl3.mozilla.com foopy53.p3.releng.scl3.mozilla.com foopy54.p3.releng.scl3.mozilla.com foopy55.p3.releng.scl3.mozilla.com foopy56.p3.releng.scl3.mozilla.com foopy57.p3.releng.scl3.mozilla.com foopy58.p3.releng.scl3.mozilla.com foopy59.p3.releng.scl3.mozilla.com The rest of p10: https://inventory.mozilla.org/en-US/systems/racks/?rack=375 mobile-imaging-010.p10.releng.scl3.mozilla.com panda-relay-005.p10.releng.scl3.mozilla.com (58-68) panda-relay-006.p10.releng.scl3.mozilla.com (70-80) panda-relay-079.p10.releng.scl3.mozilla.com (874-884) panda-relay-080.p10.releng.scl3.mozilla.com (887-909) panda-relay-001.p127.releng.scl3.mozilla.com (10-21) panda-chassis-005.p10.releng.scl3.mozilla.com panda-chassis-006.p10.releng.scl3.mozilla.com panda-chassis-079.p10.releng.scl3.mozilla.com panda-chassis-080.p10.releng.scl3.mozilla.com panda-chassis-001.p127.releng.scl3.mozilla.com foopy102.p10.releng.scl3.mozilla.com foopy103.p10.releng.scl3.mozilla.com foopy104.p10.releng.scl3.mozilla.com foopy105.p10.releng.scl3.mozilla.com foopy106.p10.releng.scl3.mozilla.com foopy107.p10.releng.scl3.mozilla.com foopy108.p10.releng.scl3.mozilla.com
Summary: please decommission foopies → please decommission panda infrastructure
At this point, the only panda infra that should be left in production is the stuff in p4, p5, and p6.
hi :sal/:vinh, do you guys think you'll have time to unrack these sometime this week? im hoping to get DDS to come pick these pandas up when they come pick up the retired hardware from phx1 arriving next week. thanks! van
Flags: needinfo?(vhua)
Flags: needinfo?(sespinoza)
unracked last week. will close once DDS picks them up
Flags: needinfo?(vhua)
Flags: needinfo?(sespinoza)
The pandas have been picked up by DDS.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.