Confirmed users
1,989
edits
ReleaseEngineering/Archive/Android Tegras: Difference between revisions
ReleaseEngineering/Archive/Android Tegras (view source)
Revision as of 12:47, 16 October 2012
, 16 October 2012→One source of truth
| Line 322: | Line 322: | ||
* if you find a tegra deployed that is not listed here, check [https://docs.google.com/spreadsheet/ccc?key=0AlIN8kWEeaF0dFJHSWN4WVNVZEhlREtUNWdTYnVtMlE&hl=en_US#gid=0 bear's master list]. If there, file a releng bug to get <tt>tegras.json</tt> updated. | * if you find a tegra deployed that is not listed here, check [https://docs.google.com/spreadsheet/ccc?key=0AlIN8kWEeaF0dFJHSWN4WVNVZEhlREtUNWdTYnVtMlE&hl=en_US#gid=0 bear's master list]. If there, file a releng bug to get <tt>tegras.json</tt> updated. | ||
* if you find a PDU not labeled per the <tt>tegras.json</tt> file, file a releng bug to update the human labels. | * if you find a PDU not labeled per the <tt>tegras.json</tt> file, file a releng bug to update the human labels. | ||
== Determining what Pandas are attached to a Chassis == | |||
At the moment, there are two ways you could look up this information: | |||
* Check the name of the relay board in the notes section for a given panda. That will also tell you the chassis name. | |||
* Use the rack-level view in inventory, like so: | |||
https://inventory.mozilla.org/en-US/systems/racks/?rack=224 | |||
You can use the rack location in the first column to identify which boards and which relay are sharing a chassis. | |||
Also, in general what you probably care more about is which relay it's attached to. Each production panda has a k/v store key of system.relay.0 that will tell you which relay it's hooked up to (which corresponds to chassis as well) and which bank and slot on the relay. | |||