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

ReleaseEngineering/How To/Set Up a Freshly Imaged Slave (view source)

387 bytes removed , 21 March 2014

no edit summary

Confirmed users

3,990

edits

@@ Line 5: / Line 5: @@
 If your machine has simply been re-imaged follow the instructions from the appropriate section.
-= Build/Try slaves=
+= Linux/MacOS X (PuppetAgain) =
-All build/try slaves require correct set of ssh keys. See below for when we must manually update them after a fresh image
+* Build/Try/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 (GPO) ==
-Host names: w64-ix-* or b-2008-ix-*
-* [[ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave|Update the ssh keys]] to the correct values for the destination pool.
-= 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) ==
+= Windows (GPO) =
-No additional steps needed. Simply add to slavealloc
+* Build/Try slaves
+** Host names: w64-ix-* or b-2008-ix-*
-== Windows 7 (GPO) ==
+** [[ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave|Update the ssh keys]] to the correct values for the destination pool.
-No additional steps needed. Simply add to slavealloc
+* Test slaves
+** Host names: t-xp32-ix, t-w732-ix, t-w864-ix
-== Windows 8 (GPO) ==
+** No additional steps needed. Simply enable on slavealloc
-No additional steps needed. Simply add to slavealloc