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

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

457 bytes removed , 8 January 2013

no edit summary

Confirmed users

3,990

edits

@@ Line 16: / Line 16: @@
 ** changing the hostname to the host's *long* (with datacenter) fully qualified domain name.
 * reboot before running puppet
-XXX: Fix fed-ref and fed64-ref to have a close enough hostname<br/>
-XXX: Remove certs from ref machine
 === Mac ===
@@ Line 40: / Line 37: @@
 {{note|For PuppetAgain slaves (e.g. HP Slaves) you should not need to do anything special for it to puppetize after a reimage. Just make sure that ~root/puppetize.log is from somepoint after it was imaged and the last lines in it do not show errors.<br>
 See [[ReleaseEngineering/PuppetAgain/Puppetization_Process|PuppetAgain Process Docs]] for the gritty details on why this is true.}}
-XXX: There is an order on when to remove certificates from the master and when to remove certs from the slave and when to test against the master. I've not figured it out if the following instructions work always. My best guess: If you get "err: Could not retrieve catalog" message, remove certs and test again without removing from the puppet master.
 Note that initial setup of puppet on slaves is very different than from buildbot masters. On slaves, the daemon is not run, rather updates are polled for when it won't impact jobs. Do not enable the standard puppet service daemon on slaves.