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

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

368 bytes removed , 21 November 2017

no edit summary

80

edits

@@ Line 19: / Line 19: @@
 = Windows (GPO) =
 == Build/Try slaves ==
-* Host names: w64-ix-* or b-2008-ix-*
+* For Build and Try there no windows hardware machines only AWS,since these are installed from golden AMIs which are created every night there should be nothing left to do here.
-* try/build(prod) machines now have their ssh keys copied via GPO. Simply enable in slavealloc.
-* It is worth verifying that the keys are set up correctly as this is relatively new (july 15, 2014)
-* '''staging machines are not setup via GPO.''' they either will have no keys or they will be given prod keys. Either way, you need to cp keys from another staging slave to the freshly imaged one via [https://wiki.mozilla.org/ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave#Staging setup staging ssh keys]
 == Test slaves ==
 * Host names: t-xp32-ix, t-w732-ix, t-w864-ix, t-w1064-ix
 * No additional steps needed. Simply enable on slavealloc