0

I've been familiarizing myself with Ansible and Puppet for use as a provisioning and configuration management tool. I may not be misunderstanding something about the way Anisble is used, but the only way I see for Ansible to ensure a consistent configuration on a regular recurring interval is to use a cron job to regularly run a playbook if I want to stick with the community sources. If I purchase Ansible Tower it looks like I can schedule playbooks there.

In comparison, when using the Puppet agent, the agent checks in with the Puppet Master on an interval, and if something has changed to deviate from what's defined on the Puppet Master, the agent will put it back as it's defined on the Puppet Master. I can do this with the community edition of Puppet if I don't have need for purchasing the commercial support.

Other than using cron jobs, is purchasing and using Ansible Tower the conventional way to use scheduled jobs to run Ansible playbooks?

Utegrad
  • 145
  • 1
  • 2
  • 8

1 Answers1

0

No. Thats because Ansible is agentless and you need some instance to trigger it.

The official way is to use Ansible Tower. But there are some alternatives:

Semaphore - Open Source Alternative to Ansible Tower https://ansible-semaphore.github.io/semaphore

Rundeck.org - Job Scheduler and Runbook Automation

flxPeters
  • 529
  • 4
  • 5