ReleaseEngineering/How To/Send a Machine For Repair: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "{{Release Engineering How To|Send a Machine For Repair}} = General = Machines slated for repair should first be cleaned of secret information - see [https://intranet.mozilla.org/...")
 
No edit summary
 
Line 3: Line 3:
Machines slated for repair should first be cleaned of secret information - see [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Clean_A_Slave_For_Shipment_Externally How To/Clean A Slave For Shipment Externally] (auth required).
Machines slated for repair should first be cleaned of secret information - see [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Clean_A_Slave_For_Shipment_Externally How To/Clean A Slave For Shipment Externally] (auth required).


In case the machine arrives back with its drive intact, any undesirable startup behaviors should be disabled.  For slaves, this means disabling the slave in slavealloc.  For masters, it means disabling the service.
Disable any undesirable startup behaviors - even if you expect the drive to be replaced, the machine may end up back on the network with its existing drive image.  For slaves, this means disabling the slave in slavealloc.  For masters, it means disabling the service.


Once everything is ready, shut the host down - Ops is much more confident un-racking a host that doesn't have spinning fans.  Provide Ops with a clear description of the host - hostname and asset tag, if possible - for un-racking and preparation for shipping.
Once everything is ready, shut the host down - Ops is much more confident un-racking a host that doesn't have spinning fans.  Provide Ops with a clear description of the host - hostname and asset tag, if possible - for un-racking and preparation for shipping.

Latest revision as of 01:39, 13 May 2011

General

Machines slated for repair should first be cleaned of secret information - see How To/Clean A Slave For Shipment Externally (auth required).

Disable any undesirable startup behaviors - even if you expect the drive to be replaced, the machine may end up back on the network with its existing drive image. For slaves, this means disabling the slave in slavealloc. For masters, it means disabling the service.

Once everything is ready, shut the host down - Ops is much more confident un-racking a host that doesn't have spinning fans. Provide Ops with a clear description of the host - hostname and asset tag, if possible - for un-racking and preparation for shipping.