canmove, Confirmed users
2,850
edits
ReleaseEngineering/Puppet/Usage: Difference between revisions
Jump to navigation
Jump to search
→Testing a slave
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) |
||
| Line 123: | Line 123: | ||
=== Testing a slave === | === Testing a slave === | ||
Puppet needs to run as root on the slaves, so equip yourself thusly and run the following command: | Puppet needs to run as root on the slaves, so equip yourself thusly and run the following command: | ||
puppetd --test --server staging-puppet.build.mozilla.org | puppetd --test --logdest console --noop --server staging-puppet.build.mozilla.org | ||
<p>This will pull updated manifests from the server, see what needs to be done, and output that. The --noop argument tells Puppet to not make any changes to the slave. Once you're satisfied with the output of that, you can run it without the --noop to have Puppet make the changes. The output should be coloured, and indicate success/fail/exception.</p> | <p>This will pull updated manifests from the server, see what needs to be done, and output that. The --noop argument tells Puppet to not make any changes to the slave. Once you're satisfied with the output of that, you can run it without the --noop to have Puppet make the changes. The output should be coloured, and indicate success/fail/exception.</p> | ||