Fix manual puppet run command docs

Change-Id: I642ad27657806403431ff109afbea8b12f2ab6d9
This commit is contained in:
James E. Blair
2016-02-24 10:44:13 -08:00
committed by Monty Taylor
parent 0b6a80ad1d
commit 60ffbab63b

View File

@@ -113,12 +113,16 @@ creation of the master repos on the gerrit server.
If an admin needs to run puppet by hand, it's a simple matter of either If an admin needs to run puppet by hand, it's a simple matter of either
logging in to the server in question and running logging in to the server in question and running
`puppet apply /opt/system-config/production/manifests/site.pp` or, on the `puppet apply /opt/system-config/production/manifests/site.pp` or, on the
puppetmaster, running puppetmaster, running:
`ansible-playbook --limit='$HOST;localhost' /opt/system-config/production/playbooks/remote_puppet_all.yaml`
.. code-block:: bash
ansible-playbook --limit='$HOST:localhost' /opt/system-config/production/playbooks/remote_puppet_else.yaml
as root, where `$HOST` is the host you want to run puppet on. If you are as root, where `$HOST` is the host you want to run puppet on. If you are
working with git, gerrit or afs servers, you'll want to replace working with git, gerrit or afs servers, you'll want to replace
`remote_puppet_all.yaml` with the appropriate specific playbook. `remote_puppet_else.yaml` with the appropriate specific playbook.
The `;localhost` is important as some of the plays depend on performing a task The `:localhost` is important as some of the plays depend on performing a task
on the localhost before continuing to the host in question, and without it in on the localhost before continuing to the host in question, and without it in
the limit section, the tasks for the host will have undefined values. the limit section, the tasks for the host will have undefined values.