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

Puppet Labs

1.1K
784
+ 1
227
Salt

419
448
+ 1
164
Add tool

Puppet Labs vs Salt: What are the differences?

Key Differences Between Puppet Labs and Salt

Puppet Labs and Salt are both configuration management tools used for managing and automating IT infrastructure. However, there are key differences between the two:

1. Scalability: Puppet Labs is known for its scalability, with the ability to manage thousands of nodes efficiently. On the other hand, Salt is designed to be highly scalable, supporting a much larger number of nodes compared to Puppet Labs.

2. Masterless vs Master/Minion Architecture: Puppet Labs follows a master/agent architecture, where the master controls and manages the agents. In contrast, Salt can be used in both master/agent mode and masterless mode, allowing for more flexibility and decentralized management.

3. Configuration Language: Puppet Labs uses Puppet Language, a declarative language that defines the desired state of config files. In contrast, Salt uses YAML or Pillar files to define configuration states. YAML is known for its simplicity and readability, while Puppet Language offers more advanced features and capabilities.

4. Remote Execution: Salt is known for its powerful remote execution capabilities, providing the ability to run commands on multiple nodes simultaneously. Puppet Labs, on the other hand, does not have built-in remote execution capabilities and relies on external tools for remote execution.

5. Integration with Cloud Services: Puppet Labs offers native integration with popular cloud platforms such as AWS and Azure, allowing for seamless management of cloud-based infrastructure. Salt also provides integration with cloud services, but its support may be more limited compared to Puppet Labs.

6. Community and Ecosystem: Puppet Labs has a larger community and ecosystem compared to Salt, with a wide range of modules and resources available for automation. While Salt also has an active community, it may have fewer available modules and resources compared to Puppet Labs.

In summary, Puppet Labs excels in scalability, native integration with cloud services, and a larger community and ecosystem, while Salt offers more flexibility in its architecture, powerful remote execution capabilities, and a simpler configuration language.

Advice on Puppet Labs and Salt
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 · 59.8K 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 · 23.6K 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
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Puppet Labs
Pros of Salt
  • 52
    Devops
  • 44
    Automate it
  • 26
    Reusable components
  • 21
    Dynamic and idempotent server configuration
  • 18
    Great community
  • 12
    Very scalable
  • 12
    Cloud management
  • 10
    Easy to maintain
  • 9
    Free tier
  • 6
    Works with Amazon EC2
  • 4
    Declarative
  • 4
    Ruby
  • 3
    Works with Azure
  • 3
    Works with OpenStack
  • 2
    Nginx
  • 1
    Ease of use
  • 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 Puppet Labs
Cons of Salt
  • 3
    Steep learning curve
  • 1
    Customs types idempotence
  • 1
    Bloated
  • 1
    Dangerous
  • 1
    No immutable infrastructure

Sign up to add or upvote consMake informed product decisions

What is 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.

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 Puppet Labs?
What companies use Salt?
See which teams inside your own company are using Puppet Labs or Salt.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Puppet Labs?
What tools integrate with Salt?

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

Blog Posts

GitHubPythonReact+42
49
40721
JavaScriptGitHubPython+42
53
21847
What are some alternatives to Puppet Labs and Salt?
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.
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.
Dotenv
It is a zero-dependency module that loads environment variables from a .env file into process.env. Storing configuration in the environment separate from code is based on The Twelve-Factor App methodology.
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.
Capistrano
Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.
See all alternatives