ReleaseEngineering/How To/Set Up a Freshly Imaged Slave: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 5: Line 5:
If your machine has simply been re-imaged follow the instructions from the appropriate section.
If your machine has simply been re-imaged follow the instructions from the appropriate section.


= Linux & MacOS X (puppet again) =
= Build/Try slaves=
Puppet does everything. You should check to make sure that ~root/puppetize.log's modified time is after the re-image time. Build machines need to have their ssh keys checked.
All build/try slaves correct set of keys on the machine. [[ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave|Update the ssh keys]] to the correct values for the destination pool


= Windows 2008 rev2 =
== Linux & MacOS X (PuppetAgain) ==
Puppet does everything. You should check to make sure that ~root/puppetize.log's modified time is after the re-image time.


== Windows 2008 rev1 (MDT & unmanaged, deprecated) ==
These machines are set up almost all the way with Group policy and only this is required to be setup after re-imaging:
* follow the [[ReferencePlatforms/Win64#Post-reimaging_steps|post reimaging]] steps.
== Windows 2008 rev2 (GPO) ==
* [[ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave|Update the ssh keys]] to the correct values for the destination pool.
* [[ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave|Update the ssh keys]] to the correct values for the destination pool.


== When moving from rev1 to rev2 ==
=== When moving from rev1 to rev2 ===
* Ensure the slavealloc "basedir" is set to c:\builds\moz2_slave
* Ensure the slavealloc "basedir" is set to c:\builds\moz2_slave
** Load this URL for your own slave (e.g. [http://slavealloc.pvt.build.mozilla.org/gettac/w64-ix-slave121 w64-ix-slave121])
** Load this URL for your own slave (e.g. [http://slavealloc.pvt.build.mozilla.org/gettac/w64-ix-slave121 w64-ix-slave121])
Line 20: Line 26:
* Ask to have the slave moved to the new Nagios 'w64r2-ix-slaves' host group via {{bug|920667}} so Nagios doesn't complain about drive E: being missing (there is no drive E: on rev2 machines).
* Ask to have the slave moved to the new Nagios 'w64r2-ix-slaves' host group via {{bug|920667}} so Nagios doesn't complain about drive E: being missing (there is no drive E: on rev2 machines).


= Windows XP (managed) =
= Test slaves =
== Linux & MacOS X (PuppetAgain) ==
Puppet does everything. You should check to make sure that ~root/puppetize.log's modified time is after the re-image time.
 
== Windows XP (GPO) ==
No additional steps needed. Simply add to slavealloc
No additional steps needed. Simply add to slavealloc


= Windows 7 (managed) =
== Windows 7 (GPO) ==
No additional steps needed. Simply add to slavealloc
No additional steps needed. Simply add to slavealloc


= Windows 8 (managed) =
== Windows 8 (GPO) ==
No additional steps needed. Simply add to slavealloc
No additional steps needed. Simply add to slavealloc
= Slavealloc notes and settings keys =
# Install the correct set of secrets on the machine. These include:
#* [[ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave|Update the ssh keys]] to the correct values for the destination pool
#* if you're troubleshooting a recently returned slave, you may want to also reverse engineer [https://wiki.mozilla.org/ReleaseEngineering/How_To/Loan_a_Slave#Cleaning How To/Clean A Slave For Shipment Externally]
# Change the slave's fields, eg production (non-try):
#* Trust: core
#* Environ: prod
#* Pool: build-scl1 (or whatever is appropriate)
# reboot it.
= Deprecated =
== Windows 2008 64-bit (MDT & unmanaged)==
These machines are set up almost all the way with Group policy and only this is required to be setup after re-imaging:
* follow the [[ReferencePlatforms/Win64#Post-reimaging_steps|post reimaging]] steps.
canmove, Confirmed users
2,850

edits

Navigation menu