Ansible, Puppet, & Chef | Day 63 (part one)

Ansible is written in [language].

Python

Ansible is [agent-based/agentless].

agentless

Puppet is [agent-based/agentless].

agent-based *with an external agent, the managed devices can be agentless

Chef is [agent-based/agentless].

agent-based

Puppet is written in [language].

Ruby

Chef is written in [language].

Ruby

Ansible uses [protocol] to connect to devices.

SSH

Chef uses [protocol] to connect to devices.

HTTPS

Puppet uses [protocol] to connect to devices.

HTTPS

Ansible uses a [push/pull] model.

push

Puppet uses a [push/pull] model.

pull

Chef uses a [push/pull] model.

pull

Ansible […] files define the actions to be taken.

playbook

Puppet […] files define the actions to be taken.

manifest

Chef […] files define the actions to be taken.

recipe / run-list

[…] clients use TCP port 8140 to communicate with the server.

Puppet

Puppet clients use […] port 8140 to communicate with the server.

TCP

Puppet clients use TCP port […] to communicate with the server.

8140

A Puppet server is called a […].

Puppet master

The Ansible server is called the […].

Control node

[Ansible/Puppet/Chef] files are written in YAML.

Ansible *templates use Jinja2

[Ansible/Puppet/Chef] files are written in a proprietary language.

Puppet / Chef

Puppet files are written in [language].

a proprietary language (known as Puppet DSL)

Chef files are written in [language].

a proprietary langage based on Ruby.

[…] uses TCP port 10002 to send configurations to clients.

Chef

Chef uses […] port 10002 to send configurations to clients.

TCP

Chef uses TCP port […] to send configurations to clients.

10002