PLAY RECAP
*************************************************************************
*****
10.10.30.171 : ok=1 changed=0
unreachable=0 failed=0
skipped=0
rescued=0 ignored=0The names of the play and the task are displayed to the
screen, as are a play recap and color-coded output based
on the status of the playbook execution. In this case, the
playbook ran successfully, as indicated by the value 1 for
the ok status. You can reuse the output of the two show
commands in the playbook to build custom automation
logic, or you can display it to the screen in JSON format
by using the -v option with the ansible-playbook
command.
Puppet
Puppet is a configuration management tool used to
automate configuration of servers and network devices.
Puppet was founded in 2005, making it one of the most
venerable automation tools on the market today. It was
created as an open-source project—and it still is today,
but it is also available as a commercial offering called
Puppet Enterprise that was created by Puppet Labs in
- It is written in Ruby and defines its automation
instructions in files called Puppet manifests. Whereas
Ansible is agentless, Puppet is agent based. This means
that a software agent needs to be installed on each device
that is to be managed with Puppet. This is a drawback for
Puppet as there are instances of network devices in
which third-party software agents cannot be easily
installed. Proxy devices can be used in these situations,
but the process is less than ideal and means Puppet has a
greater barrier to entry than other automation tools.
Puppet is architected in a client/server manner, with the
client being the software agent running on the managed
devices and the server being the main Puppet server,