Need advice about which tool to choose?Ask the StackShare community!
Pallet vs Puppet Labs: What are the differences?
Developers describe Pallet as "Automates controlling and provisioning cloud server instances. DevOps for the JVM". The machines being managed require no special dependencies to be installed. As long as they have bash and ssh running, they can be used with pallet. Pallet has no central server to set up and maintain - it simply runs on demand. You can run it from anywhere, even over a remote REPL connection. On the other hand, Puppet Labs is detailed as "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.
Pallet and Puppet Labs can be primarily classified as "Server Configuration and Automation" tools.
Some of the features offered by Pallet are:
- Everything in Version Control
- Jar File Distribution of Crates
- Provisioning, Configuration and Administration
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.
Pallet and Puppet Labs are both open source tools. Puppet Labs with 5.37K GitHub stars and 2.1K forks on GitHub appears to be more popular than Pallet with 802 GitHub stars and 122 GitHub forks.
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?
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.
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.
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.
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.
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.
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
Pros of Pallet
Pros of Puppet Labs
- Devops52
- Automate it44
- Reusable components26
- Dynamic and idempotent server configuration21
- Great community18
- Very scalable12
- Cloud management12
- Easy to maintain10
- Free tier9
- Works with Amazon EC26
- Declarative4
- Ruby4
- Works with Azure3
- Works with OpenStack3
- Nginx2
- Ease of use1
Sign up to add or upvote prosMake informed product decisions
Cons of Pallet
Cons of Puppet Labs
- Steep learning curve3
- Customs types idempotence1
Sign up to add or upvote consMake informed product decisions
What is Pallet?
What is Puppet Labs?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Pallet?
What companies use Puppet Labs?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Pallet?
What tools integrate with Puppet Labs?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+42
+42