When comparing SaltStack vs Puppet , the Slant community recommends SaltStack for most people. In the question“What are the best configuration management tools?” SaltStack is ranked 3rd while Puppet is ranked 4th. The most important reason people chose SaltStack is:
Salt has an impressive welcoming and active community of users. There are user groups all over the world (Stockhom, Silicon Valley, Paris, and lots more), and an active [live chat.](http://saltstack.com/community/)
Ranked in these QuestionsQuestion Ranking
Pro Friendly and open community
Salt has an impressive welcoming and active community of users. There are user groups all over the world (Stockhom, Silicon Valley, Paris, and lots more), and an active live chat.
Pro Easy to read output
Salt's configuration files and setups are organized into YAML files. This makes them very easy to read and understand since YAML is considered very readable.
Pro Agentless via SSH is an option
Salt can run agentless just like ansible, allowing it to manage devices that you can't run an agent on (routers/switches, etc).
Pro Communicates through SSH or agents
Salt can communicate with clients through agents called minions, or through SSH.
With Salt you can have multiple layers of masters which result in an arrangement which distributes load and increases redundancy. Upstream masters can then control downstream masters and their minions.
Salt has support for Windows, Linux and Unix. Though it's fair to say that it's easier to use and it's more useful in Unix and Linux systems.
Pro Fast execution of commands
Salt works around a Salt master which has multiple agents (Salt minions) that have a persistent connection to the master. Because of this persistent connection, commands to the master are fast to reach the minions. Furthermore, the minions also save various data to the cache in order to make execution faster.
When compared against other tools to run the same actions, Salt almost always completes the actions in significantly less time.
Pro Declarative sematic
You define the state the server should be in and Puppet transforms it that state. This is opposed to explicitly declaring a list of actions to be performed.
If a developer wants more flexibility and control there's always the option of falling back to explicitly running commands but that's discouraged.
Puppet is a complete solution in terms of available features and modules. It has full support for all the main Operating Systems and provides lots of tools for its users.
Pro Large helpful community
Puppet is very mature and relatively old. This means that it has gathered quite a following over the years. This large community means that there are a lot of modules, guides and configuration recipes ready to use built by the community.
Pro All-in-one Package since version 4
With Facter, Collective and Hiera.
Pro Broad cross-platform support
Puppet is supported on a wide range of operating systems. See the Docs for a complete list.
Pro Helpful UI
Puppet's UI is very useful. It allows real-time control of managed nodes by using modules and configuration recipes that are on the master servers. Although the UI is great for management, it lacks when trying to configure modules.
Pro Easy to learn
Puppet is model-driven and easier for diverse teams (that may include non-devs) to learn than it's main competitor, Chef.
Con Solid knowledge of Ruby is needed to create your own modules
Modules and configurations are written in a specific language based on Ruby or in Ruby itself. So in order to be able to create custom configuration and modules you need a solid knowledge of Ruby.
Although it's fair to mention that there are many modules already available for every use-case.
Con Does not enforce policy when the puppetmaster is offline
Does not enforce policy when the puppetmaster is offline, does have a caching mechanism but since it does not include any files that need to be transfer it basically does not work
Con Slow as hell
Compared with other CM tools it's very slow and needs to do a lot of caching to give it the impression that it's fast (which it's not)
Con Syntax is a mess
To use puppet to the full extent you need to know the following tools; most of them are an integral part of puppet, Ruby, Ruby templates, puppet DSL, Hiera, Facter and Mcollective which all have a different syntax
Con Interaction between modules can get quite complex very fast
Due to it's out of order execution you can easily get into race condition between different modules. You have to be very careful declaring pre-requisites for the tasks so they don't step on top of each other. On the other hand when you get this lets you deploy things much faster than straight line execution tools
Con Lacks flexibility
The lack of control over Puppet's model-driven approach can result in less flexibility and power from the tool.