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

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

86 bytes removed , 21 November 2017

no edit summary

80

edits

@@ Line 11: / Line 11: @@
 These are installed from golden AMIs created every night. There should be nothing for you to do here.
 == Linux Talos slaves ==
-After puppet is run, these hardware slaves need to have httpd restarted to pick-up the contents of talos.conf until {{bug|1141416}} is fixed:
+After puppet is run, nothing else is needed.The machine can be returned back to service by simply enable in slavealloc.
-  # root@talos-linux64-ix-001
+You should check to make sure that ~root/puppetize.log's modified time is after the re-image time.
-  service apache2 restart
-You can also just reboot the machine one extra time before returning it to service as this accomplishes the same thing.
 == Mac test slaves ==
 Puppet does everything. You should check to make sure that ~root/puppetize.log's modified time is after the re-image time.
 = Windows (GPO) =
@@ Line 25: / Line 24: @@
 * '''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
+* Host names: t-xp32-ix, t-w732-ix, t-w864-ix, t-w1064-ix
 * No additional steps needed. Simply enable on slavealloc