Ansible vs Puppet Labs

Need advice about which tool to choose?Ask the StackShare community!

Ansible

14.4K
11.5K
+ 1
1.3K
Puppet Labs

818
701
+ 1
224
Add tool

Ansible vs Puppet Labs: What are the differences?

Ansible: Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine. Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use; Puppet Labs: Server automation framework and application. Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Ansible and Puppet Labs belong to "Server Configuration and Automation" category of the tech stack.

Some of the features offered by Ansible are:

  • Ansible's natural automation language allows sysadmins, developers, and IT managers to complete automation projects in hours, not weeks.
  • Ansible uses SSH by default instead of requiring agents everywhere. Avoid extra open ports, improve security, eliminate "managing the management", and reclaim CPU cycles.
  • Ansible automates app deployment, configuration management, workflow orchestration, and even cloud provisioning all from one system.

On the other hand, Puppet Labs provides the following key features:

  • Insight- Puppet Enterprise's event inspector gives immediate and actionable insight into your environment, showing you what changed, where and how by classes, nodes and resources.
  • Discovery- Puppet Enterprise delivers a dynamic and fully-pluggable discovery service that allows you to take advantage of any data source or real-time query results to quickly locate, identify and group cloud nodes.
  • Provisioning- Automatically provision and configure bare metal, virtual, and private or public cloud capacity, all from a single pane. Save time getting your cloud projects off the ground by reusing the same configuration modules you set up for your physical deployments.

"Agentless" is the primary reason why developers consider Ansible over the competitors, whereas "Devops" was stated as the key factor in picking Puppet Labs.

Ansible and Puppet Labs are both open source tools. Ansible with 38.2K GitHub stars and 16K forks on GitHub appears to be more popular than Puppet Labs with 5.37K GitHub stars and 2.1K GitHub forks.

According to the StackShare community, Ansible has a broader approval, being mentioned in 960 company stacks & 587 developers stacks; compared to Puppet Labs, which is listed in 180 company stacks and 49 developer stacks.

Advice on Ansible and Puppet Labs
Rogério R. Alcântara
Needs advice
on
Puppet LabsPuppet LabsChefChef
and
AnsibleAnsible
in

Personal Dotfiles management

Given that they are all “configuration management” tools - meaning they are designed to deploy, configure and manage servers - what would be the simplest - and yet robust - solution to manage personal dotfiles - for n00bs.

Ideally, I reckon, it should:

  • be containerized (Docker?)
  • be versionable (Git)
  • ensure idempotency
  • allow full automation (tests, CI/CD, etc.)
  • be fully recoverable (Linux/ macOS)
  • be easier to setup/manage (as much as possible)

Does it make sense?

See more
Replies (3)
terry chay
Principal Engineer at RaiseMe · | 9 upvotes · 39.1K views
Recommends
AnsibleAnsible

I recommend whatever you are most comfortable with/whatever might already be installed in the system. Note that, for personal dotfiles, it does not need to be containerized or have full automation/testing. It just needs to handle multiple OS and platform and be idempotent. Git will handle the heavy lifting. Note that you'll have to separate out certain files like the private SSH keys and write your CM so that it will pull it from another store or assist in manually importing them.

I personally use Ansible since it is a serverless design and is in Python, which I prefer to Ruby. Saltstack was too new when I started to port my dotfile management scripts from shell into a configuration management tool. I think any of the above is fine.

See more
Recommends
SaltSalt

You should check out SaltStack. It's a lot more powerful than Puppet, Chef, & Ansible. If not Salt, then I would go Ansible. But stay away from Puppet & Chef. 10+ year user of Puppet, and 2+ year user of Chef.

See more
Attila Fulop
Management Advisor at artkonekt · | 3 upvotes · 4.4K views
Recommends

Chef is a definite no-go for me. I learned it the hard way (ie. got a few tasks in a prod system) and it took quite a lot to grasp it on an acceptable level. Ansible in turn is much more straightforward and much easier to test.

See more
Needs advice
on
Puppet LabsPuppet LabsChefChef
and
AnsibleAnsible

I'm just getting started using Vagrant to help automate setting up local VMs to set up a Kubernetes cluster (development and experimentation only). (Yes, I do know about minikube)

I'm looking for a tool to help install software packages, setup users, etc..., on these VMs. I'm also fairly new to Ansible, Chef, and Puppet. What's a good one to start with to learn? I might decide to try all 3 at some point for my own curiosity.

The most important factors for me are simplicity, ease of use, shortest learning curve.

See more
Replies (2)
Recommends
AnsibleAnsible

I have been working with Puppet and Ansible. The reason why I prefer ansible is the distribution of it. Ansible is more lightweight and therefore more popular. This leads to situations, where you can get fully packaged applications for ansible (e.g. confluent) supported by the vendor, but only incomplete packages for Puppet.

The only advantage I would see with Puppet if someone wants to use Foreman. This is still better supported with Puppet.

See more
Gabriel Pa
Recommends
KubernetesKubernetes
at

If you are just starting out, might as well learn Kubernetes There's a lot of tools that come with Kube that make it easier to use and most importantly: you become cloud-agnostic. We use Ansible because it's a lot simpler than Chef or Puppet and if you use Docker Compose for your deployments you can re-use them with Kubernetes later when you migrate

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More