Closed
Bug 918168
(tegra-decomm)
Opened 11 years ago
Closed 11 years ago
Decomission Problem Tegras
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Unassigned)
References
Details
I'm filing in buildduty for now, and taking, but this is to help track which tegras need to be decomm'd due to recovery attempts not working, or never taking good jobs, etc.
Will move to other products when we're ready for a batch-worthy action
Comment 1•11 years ago
|
||
"All of them"? ;-)
On a more serious note, I'm sure Phil has some suggestions here...
Reporter | ||
Comment 2•11 years ago
|
||
...and with that this bug is actionable, not sure what method would be the best plan of action though considering impending move...
Few options that come to my mind:
* Do nothing and let movers pack them to bring to scl3, just don't plug in in scl3
* Place sticky notes - or red tape across homes for these while in mtv1, movers don't pack them.
* physically pull out of mtv1 production wiring ~now, to clear the room for when movers come.
All those options, and others I haven't thought of are acceptable to releng. I'd just love to know the plan-of-record once you decide on it.
Assignee: bugspam.Callek → server-ops-dcops
Component: Buildduty → Server Operations: DCOps
Flags: needinfo?(dmoore)
Product: Release Engineering → mozilla.org
QA Contact: armenzg → dmoore
Version: unspecified → other
Comment 3•11 years ago
|
||
Thanks for the work, Callek. I think your third option is the most desirable for DCOps. It removes any confusion about how to handle and track these boards during the upcoming move.
Flags: needinfo?(dmoore)
Updated•11 years ago
|
colo-trip: --- → mtv1
Comment 4•11 years ago
|
||
removed from nagios.
Comment 5•11 years ago
|
||
All tegras above removed from their original location
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•