98b7ea710b
Newer ansible (2.7) is far more picky about always blocks being a part of block blocks. This means you cannot have a set of when conditions apply to a standalone always block. Fix our use of this by putting our always block in the run puppet block then move the always tasks into a block of their own with a condition set. Change-Id: I50988b6b312e4d00b73ca4454e0420913d4ae181 |
||
---|---|---|
defaults | ||
handlers | ||
library | ||
meta | ||
tasks | ||
templates | ||
tests | ||
vars | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
README.md | ||
bindep.txt | ||
requirements.txt | ||
run_tests.sh | ||
test-requirements.txt | ||
tox.ini |
README.md
puppet
Run puppet consistently from ansible.
Requirements
puppet needs to be installed on the target node, and if puppet agent is being used, the cert exchange needs to have been performed.
Role Variables
Either puppetmaster or manifest should be supplied. If you are using puppet agent, you want to supply puppetmaster. If you are using puppet apply, you want to supply manifest.
Dependencies
None
Example Playbook using a puppetmaster
The only required argument is puppetmaster:
- hosts: servers
roles:
- { role: puppet, puppetmaster: puppetmaster.openstack.org }
Example Playbook without a puppetmaster
The only required argument is manifest:
- hosts: servers
roles:
- { role: puppet, manifest: /opt/system-config/production/manifests/site.pp }
License
Apache
Author Information
ansible-puppet is maintained by the OpenStack Infra team. The best way to contact them is on #openstack-infra on freenode.