960065 - tegra and panda decomm

Status: RESOLVED FIXED

(Infrastructure & Operations :: DCOps, task)

Description

[[e-mail] (:bhearsum)]

Let's collect a few before we go about this.

Comment 1

[[e-mail] (:bhearsum)]

Attachment: remove from buildbot-configs

Looks like we don't remove pandas...

Comment 2

[Justin Wood (:Callek)]

Comment on attachment 8360465 [details] [diff] [review]
remove from buildbot-configs

stamp+

We could remove pandas too, I just think it can cause a mess like we currently have for tegras, so easier to avoid.

Comment 3

[[e-mail] (:bhearsum)]

Attachment: remove from devices.json

Comment 4

[Justin Wood (:Callek)]

Comment on attachment 8360467 [details] [diff] [review]
remove from devices.json

Review of attachment 8360467 [details] [diff] [review]:
-----------------------------------------------------------------

stamp+, but when you check this in can you also ssh to the foopies and `rm -rf /builds/<device>` as well as kill any procid's with <device> in the filepath/grep (e.g. `ps auxwww | grep tegra-078` --> kill <pids>)

Comment 5

[[e-mail] (:bhearsum)]

Marked as decomm in slavealloc, too.

Comment 6

[[e-mail] (:bhearsum)]

All the RelEng stuff is done now - DCops - can you do whatever you do for decomm on the 5 machines in the blocking field?

Comment 7

[Van Le [:van]]

tegra decommed. over to scl1 for panda decomms.

Comment 8

[Vinh Hua [:vinh]]

All pandas have been decommed and updated in inventory.  Only item left is the tegra-078 in scl3.

Comment 9

[Vinh Hua [:vinh]]

Inventory updated for decomm tegra-078.

Comment 10

[Van Le [:van]]

tegra removed from DNS.