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

Ansible

19.1K
15.4K
+ 1
1.3K
Salt

418
448
+ 1
164
Add tool

Ansible vs Salt: What are the differences?

Introduction:

Ansible and Salt are both popular configuration management tools used in IT infrastructure automation. While they serve similar purposes, there are key differences between Ansible and Salt that set them apart. In this article, we will explore these differences and highlight their distinct features.

  1. Architecture: Ansible follows a centralized architecture, where a master node controls and manages the entire infrastructure. On the other hand, Salt uses a master-minion architecture, where a master node communicates and controls multiple minion nodes. This allows for more efficient distribution of work and faster execution of tasks.

  2. Language: Ansible uses a declarative language called YAML (Yet Another Markup Language) for defining tasks and configurations. It focuses on simplicity and readability, making it easy for users to understand and use. In contrast, Salt uses a more flexible and powerful scripting language called Jinja and utilizes Python for complex tasks, granting users greater control and customization options.

  3. Scalability: When it comes to scalability, Salt has an edge over Ansible. Salt's master-minion architecture allows for easy scaling by adding more minion nodes, which can handle an extensive number of parallel tasks. In Ansible, the centralized architecture might face challenges when dealing with a large number of hosts, as it relies on SSH connections and can be slower in execution.

  4. Remote Execution: One notable difference between Ansible and Salt is their remote execution mechanism. Ansible establishes SSH connections to the remote hosts and performs tasks over SSH, making it more suitable for environments with strict security policies. In contrast, Salt uses its own communication protocol called ZeroMQ, enabling faster and more efficient remote execution with minimal network overhead.

  5. Extensibility: While both Ansible and Salt provide a rich set of predefined modules and states, Salt offers greater extensibility through its custom execution modules and state modules. This allows users to easily create their own modules or leverage existing Python code for complex configurations, providing more flexibility and customization options compared to Ansible.

  6. Community and Ecosystem: Ansible boasts a larger and more established community, which contributes to its extensive collection of community-developed roles and playbooks readily available for use. Salt, although rapidly growing, has a smaller community but offers a flexible event-driven framework and provides more advanced features like event-driven orchestration and remote execution.

In summary, Ansible and Salt, while sharing similar goals, differ in architecture, language, scalability, remote execution mechanism, extensibility, and community support. These differences allow users to choose the tool that best suits their specific requirements and preferences.

Advice on Ansible and Salt
Needs advice
on
AnsibleAnsible
and
RundeckRundeck

We have a lot of operations running using Rundeck (including deployments) and we also have various roles created in Ansible for infrastructure creation, which we execute using Rundeck. Rundeck we are using a community edition. Since we are already using Rundeck for executing the Ansible role, need an advice. What difference will it make if we replace Rundeck with Ansible Tower? Advantages and Disadvantages? We are using Jenkins to call Rundeck Job, same will be used for Ansible Tower if we replace Rundeck.

See more
Replies (1)
Denis Gukov

I never use Tower, but I can recommend Ansible Semaphore as alternative to Rundeck. It is lightweight, easy to use and tailored for work with Ansible.

See more
Rogério R. Alcântara
Needs advice
on
AnsibleAnsibleChefChef
and
Puppet LabsPuppet Labs
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 · 63.4K views
Recommends
on
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
on
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 · 26.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
AnsibleAnsibleChefChef
and
Puppet LabsPuppet Labs

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
on
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
on
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
Decisions about Ansible and Salt
Hendrik Halkow

Terraform provides a cloud-provider agnostic way of provisioning cloud infrastructure while AWS CloudFormation is limited to AWS.

Pulumi is a great tool that provides similar features as Terraform, including advanced features like policy and cost management.

We see that Terraform has great support in the cloud community. For most cloud services we use, there is an official Terraform provider. We also believe in the declarative model of HCL, which is why we chose Terraform over Pulumi. However, we still keep an eye on Pulumi's progress.

Ansible is great for provisioning software and configuration within virtual machines, but we don't think that Ansible is the right tool for provisioning cloud infrastructure since it's built around the assumption that there is an inventory of remote machines. Terraform also supports more services that we use than Ansible.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Ansible
Pros of Salt
  • 284
    Agentless
  • 210
    Great configuration
  • 199
    Simple
  • 176
    Powerful
  • 155
    Easy to learn
  • 69
    Flexible
  • 55
    Doesn't get in the way of getting s--- done
  • 35
    Makes sense
  • 30
    Super efficient and flexible
  • 27
    Powerful
  • 11
    Dynamic Inventory
  • 9
    Backed by Red Hat
  • 7
    Works with AWS
  • 6
    Cloud Oriented
  • 6
    Easy to maintain
  • 4
    Vagrant provisioner
  • 4
    Simple and powerful
  • 4
    Multi language
  • 4
    Simple
  • 4
    Because SSH
  • 4
    Procedural or declarative, or both
  • 4
    Easy
  • 3
    Consistency
  • 2
    Well-documented
  • 2
    Masterless
  • 2
    Debugging is simple
  • 2
    Merge hash to get final configuration similar to hiera
  • 2
    Fast as hell
  • 1
    Manage any OS
  • 1
    Work on windows, but difficult to manage
  • 1
    Certified Content
  • 46
    Flexible
  • 30
    Easy
  • 27
    Remote execution
  • 24
    Enormously flexible
  • 12
    Great plugin API
  • 10
    Python
  • 5
    Extensible
  • 3
    Scalable
  • 2
    nginx
  • 1
    Vagrant provisioner
  • 1
    HipChat
  • 1
    Best IaaC
  • 1
    Automatisation
  • 1
    Parallel Execution

Sign up to add or upvote prosMake informed product decisions

Cons of Ansible
Cons of Salt
  • 8
    Dangerous
  • 5
    Hard to install
  • 3
    Doesn't Run on Windows
  • 3
    Bloated
  • 3
    Backward compatibility
  • 2
    No immutable infrastructure
  • 1
    Bloated
  • 1
    Dangerous
  • 1
    No immutable infrastructure

Sign up to add or upvote consMake informed product decisions

What is Ansible?

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.

What is Salt?

Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.

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

What companies use Ansible?
What companies use Salt?
Manage your open source components, licenses, and vulnerabilities
Learn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Ansible?
What tools integrate with Salt?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

PythonDockerKubernetes+14
12
2651
GitGitHubSlack+30
27
18684
JavaScriptGitGitHub+33
20
2140
GitHubDockerAmazon EC2+23
12
6610
JavaScriptGitHubPython+42
53
22147
What are some alternatives to Ansible and Salt?
Puppet Labs
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.
Chef
Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.
Terraform
With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
AWS CloudFormation
You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.
See all alternatives