canmove, Confirmed users
2,850
edits
ReleaseEngineering/How To/Set Up a Freshly Imaged Slave: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Set Up a Freshly Imaged Slave (view source)
Revision as of 15:07, 13 August 2015
, 13 August 2015→Linux/MacOS X (PuppetAgain)
ChrisCooper (talk | contribs) |
|||
| Line 6: | Line 6: | ||
= Linux/MacOS X (PuppetAgain) = | = Linux/MacOS X (PuppetAgain) = | ||
== 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. | |||
== Linux AWS slaves == | |||
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: | |||
# root@talos-linux64-ix-001 | |||
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. | Puppet does everything. You should check to make sure that ~root/puppetize.log's modified time is after the re-image time. | ||