Puppet Enteprise is an IT automation and configuration management solution that enables users to manage and automate infrastructure and complex workflows. The vendor states Puppet Enterprise combines both model‑based and task-based capabilities in a way that enables organizations to scale their multi-cloud infrastructure as their automation footprint grows, with more flexibility from both agent-based and agentless capabilities.
N/A
Ansible
Score 9.1 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
As I mentioned before Ansible is a great tool. There is no question about it. It has very simple syntax (YAML), is very easy to learn, and is scalable as well. But the only thing that Ansible lacked at that time was the actual agent that have to go into each server. Ansible …
I have not used any other Configuration Management System since cfengine back in about 2007 so I have little current input on alternatives to Puppet having never used them, though Chef seems to have gained some traction as has Ansible.
Puppet has a very wide user base with many organizations tht support it as well as conferences and events. Puppet DSL is based in Ruby while the server is now in Clojure providing ease of configuration with the power of scale. Puppet is a great entry point into the world of …
One of these is already included in our license and the other is not. The agent based model makes access management to servers simpler. The agentless model makes things more flexible and secure for large organizations
Puppet has Red Hat Ansible Automation Platform beat on metrics. This isn't a fair comparison due to the agent oriented nature of puppet. Ansible is much smoother to start using and appreciably faster to install, configure and role into small groups of systems. I no longer use …
We were Puppet users. Red Hat Ansible Automation Platform made more sense to us because of the focus on Ansible content to support our AIX systems and RHEL systems. We have also seen that the learning curve for Red Hat Ansible Automation Platform is better than we experienced …
It was much simpler to deploy and use Red Hat Ansible Automation Platform in our enterprise environment. Red Hat has great training to get our users up to speed. YAML is easy to write (although watch out for spacing) and run playbooks. We can easily generate infrastructure …
All three of these competitors are agent based. I did not want an additional service that needed to run absolutely everywhere. I also did not want to maintain a load balanced cluster of master servers that grows in resource requirements as your infrastructure scales.
Ansible is much easier than Puppet, more enterprises are switching from Puppet to Ansible due to ease of use. Ansible has integration modules which allow you to transition from Puppet or Chef to Ansible. IT Automation space has a CAGR of 200%+ what are you doing to not get left …
Ansible has unique features in terms of server managing and configuring. It is easy to use and fits the Red Hat Linux well since they are closely related. Our servers are mostly Red Hat, so it makes sense to use Ansible. But we are still exploring which is the best.
Ansible is a great product, which we really love as it is compatible running along side and with other DevOps tool. The integration features allows other teams to participate in our shared objective. Ansible is easy to use as many programmers are familiar with Python and RHEL. …
In the time of integration, we chose Ansible instead of Puppet because it was simpler to use, based on Python and didn't require additional server environments to run. Of course, there are a lot of different alternatives like Chef or Salt Stack.
Ansible is sufficient for our purposes because our configurations are relatively simple. Chef and Puppet would work better for more complex configurations. Also, our applications are deployed using Docker which simplifies our configuration requirements. An organization with …
I haven't used Puppet personally, but I believe Ansible is a robust solution which can serve many purposes. Puppet I'm sure is customizable in similar ways, I just don't have the experience to speak intelligently on the subject.
I have used Puppet, Chef during my career and Ansible seems to be the most efficient tool by far, in terms of its implementation, configuration and ease of use.
Puppet is good enough to get the job done, you can use it to automate deployments and maintain files and configurations, if this is all you're looking for it's great. If you're looking for more control over your systems as a whole without having to write your own scripts or install multiple configuration management systems then Puppet is not what you're looking for.
Anything Infrastructure is the best case scenario for Ansible use cases. The agentless feature of Ansible is one of its best selling points as it allows core Ansible to be supported on nearly any platform via any interface. AAP is a great solution for company's doing adhoc automation. It essentially brings the wild-west into the modern age by providing enterprise-grade capabilities such as API, scheduling, secure vault, centralized logging, RBAC, inventories, and more!
Easy to read sets of instructions to do various things in and out of a pipeline.
Templating
Cloud and on prem provisioning.
Scalability and reusability.
We use it for everything from provisioning hardware for deploying software to it to running pipelines and building containers, etc. It's readable, easy to scale, and great for creating re-usable templates, scripts, or instructions.
The setup of Puppet is a nightmare compared to ansible. Anyone watching a youtube video can easily set up ansible with minimal IT knowledge. All one needs is the source IP addresses and we are good to go. Setting up Puppet is a more hands-on task and pushing the puppet agents to all the boxes is another issue. If the installation and setup were simplified like ansible that would attract a lot of people to this platform
The syntax of the code for Puppet is not as easy as ansible. Ansible simply follows a YAML format and it's like typing in normal English. Even complicated tasks can be written by just understanding YAML syntax. Perhaps Puppet needs to revisit the lanugage used and try to come up with a much simpler lanugage for writing code. This will make day-to-day usage easier.
We are extremely happy with the use of AAP. It's better than expected, There is almost no limit when thinking of automation. The only problem is that the day to day is consuming a big part of our time. Patching and checking vulnerabilities are virtually killing us. But we can only improve with AAP.
Overall, the product is excellent, with daily-use features for both large and small infrastructure. Ansible does its job quickly and ensures compliance, keeping the environment up to date and safe from open vulnerabilities. Large-scale inventory management and license management. Industry standard followed by best practices to maintain continuity. Budget-friendly compared to other products.
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
Puppet has top class support. You can simply mail them with their query and they will respond to your query in a timely manner. We do have enterprise license for puppet. Also there is a vibrant community for puppet out there. So even if you dont purchase a premium support option you can simply google your queries and get answers
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
HPSA is a licensed product and incurs significant upfront investment costs due to COTS licensing. Puppet Data Center Automation has a significantly lower upfront investment and product documentation is more readily available. Chef is a very similar offering, however, at the time our decision was considered, the adoption of Chef vs. Puppet was significantly less in the community.
AAP compares favorably with Terraform and Power Automate. I don't have much experience with Terraform, but I find AAP and Ansible easier to use as well as having more capabilities. Power Platform is also an excellent automation tool that is user friendly but I feel that Ansible has more compatibility with a variety of technologies.
First, it keeps our entire server infrastructure aligned with our standards and reduces the time and effort needed to maintain our systems.
Automate routine IT tasks to save time, reduce errors, and ensure every server is configured and updated consistently.
Tasks that used to take our teams weeks to complete manually now run automatically and reliably, with full visibility, making our infrastructure management more effective and our compliance tracking much easier.