Closed Bug 1043938 Opened 10 years ago Closed 10 years ago

Decommission foopy117 and associated tegras

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pmoore, Assigned: Callek)

References

Details

Attachments

(1 file)

We need to decommission foopy117 (see bug 1037441), so let's decomm the tegras on this foopy at the same time (tegra-105, tegra-107, tegra-108, tegra-109, tegra-110, tegra-111, tegra-113, tegra-114, tegra-115, tegra-117).

Since we are moving off the tegra platform there should be no reason to relocate these tegras.

Steps I can think of:

1) decommission tegras in slavealloc
2) remove tegras from devices.json
3) update slave tracking bugs for all 10 tegras to say they are decommissioned
4) create a decommission bug for relops (or use this one, but reassign to relops) for foopy117 plus the 10 tegras

Have I missed anything?

Pete
A separate (cloned?) bug would work better for us (and we'll make another one for dcops for the physical hardware).
Blocks: 1045675
Attached patch [tools] v1Splinter Review
Assignee: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #8464053 - Flags: review?(pmoore)
Comment on attachment 8464053 [details] [diff] [review]
[tools] v1

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

Thanks Callek!
Attachment #8464053 - Flags: review?(pmoore) → review+
Cool, all seem to have been removed from slavealloc too
Thanks Callek!
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: