Confirmed users
1,989
edits
ReleaseEngineering/Archive/Android Tegras: Difference between revisions
ReleaseEngineering/Archive/Android Tegras (view source)
Revision as of 22:20, 19 February 2013
, 19 February 2013→Moving replacement pandas into production
| Line 301: | Line 301: | ||
Pandas die and the hardware needs to be replaced. DC Ops have several spare pandas they use for replacement purposes. The new pandas will have a different hostnames that the old ones. The procedure to replace a dead panda from the releng side is: | Pandas die and the hardware needs to be replaced. DC Ops have several spare pandas they use for replacement purposes. The new pandas will have a different hostnames that the old ones. The procedure to replace a dead panda from the releng side is: | ||
* If the panda is used for Android tests, it needs to be imaged in Lifeguard with the android image. After the | * If the panda is used for Android tests, it needs to be imaged in Lifeguard with the android image. After the imaging process has completed, you need to set its status to "locked_out". | ||
* Since the hostnames are different, the range of pandas allocated to production may need to be modified in mozilla-tests/production_config.py. | * Since the hostnames are different, the range of pandas allocated to production may need to be modified in mozilla-tests/production_config.py. | ||
* The devices.json file needs to be modified to remove the old panda's definition and include the new pandas. See {{bug|841486}} for an example of the changes required. See https://bugzilla.mozilla.org/show_bug.cgi?id=836857#c2 for an example of the old to new panda mapping from DC Ops. | * The devices.json file needs to be modified to remove the old panda's definition and include the new pandas. See {{bug|841486}} for an example of the changes required. See https://bugzilla.mozilla.org/show_bug.cgi?id=836857#c2 for an example of the old to new panda mapping from DC Ops. | ||