Closed
Bug 664624
Opened 13 years ago
Closed 13 years ago
script to power-cycle a tegra without a browser
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
Attachments
(1 file)
4.72 KB,
patch
|
bear
:
review+
|
Details | Diff | Splinter Review |
A bit of Python to add to the tegra-management equipment so that we can power-cycle a tegra without clicking through the annoying PDU web interface.
Assignee | ||
Comment 1•13 years ago
|
||
For the record, I used tegra-069 and tegra-024 to test this.
Assignee | ||
Comment 2•13 years ago
|
||
What do you think? Is the caching in the current directory OK? How about error handling? The Telnet object has a timeout, so this shouldn't hang indefinitely even if the PDU behaves badly. It will raise some sort of exception, although I don't know what. Any other changes I should make?
Attachment #540662 -
Flags: review?(bear)
Comment 3•13 years ago
|
||
Comment on attachment 540662 [details] [diff] [review] m664624-tools-p1-r1.patch There are some small nits but none big enough to not r+ it so we can start testing. I do think that the pdu - tegra linking needs to be changed, but that's because I'm in the middle of changing :) I'm creating a *.json file that contains every tegra and what foopy and pdu it belongs to - so I would like to switch to that. I would prefer that the telnet call be wrapped with a pretty greedy try/except so that anything except a connect would just fail out the whole call. Looks good - thanks
Attachment #540662 -
Flags: review?(bear) → review+
Assignee | ||
Comment 4•13 years ago
|
||
committed
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•