Skip to main content
TrustRadius
Puppet Enterprise

Puppet Enterprise

Overview

What is Puppet Enterprise?

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…

Read more
Recent Reviews

TrustRadius Insights

Puppet is a versatile tool that is widely used across organizations to streamline operations and automate various tasks. Users rely on …
Continue reading

Puppet is a great tool

9 out of 10
February 12, 2016
Incentivized
We use Puppet Data Center Automation as a configuration management tool in our organization. It allows us to maintain a constant baseline …
Continue reading
Read all reviews
Return to navigation

Product Demos

Puppet Enterprise Demo - Silicon Valley Puppet Camp 2014

YouTube

Demo of Puppet Enterprise Supported Modules

YouTube

Keep your IT infrastructure in a known good state with Puppet Enterprise

YouTube

Puppe Enterprise Openstack Icehouse Demo

YouTube

Puppet Enterprise 2019 Console Walkthrough Demo

YouTube

Automate IT: Getting Started with Puppet Enterprise

YouTube
Return to navigation

Product Details

Puppet Enterprise Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(53)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Puppet is a versatile tool that is widely used across organizations to streamline operations and automate various tasks. Users rely on Puppet to maintain configuration and deploy new versions of applications throughout their infrastructure. With variables stored in Hiera, Puppet allows for easy roll-out of configuration changes across all parts of the system. It also serves as a reliable deployment tool, enabling quick and consistent deployment and maintenance of various systems.

One of the key use cases of Puppet is automating redundant tasks and simplifying the deployment of complex system configurations. By automating installations and configuring environments after the initial OS install, Puppet greatly reduces manual effort and ensures consistent configurations. Additionally, Puppet is utilized to automate deployments and ensure configuration consistency across multiple data centers, making it scalable and efficient.

Another important use case is managing server lifecycle and automating provisioning, configuration changes, and removal of dynamic resources. Puppet Data Center Automation is particularly useful in standardizing server deployments, maintaining a uniform configuration, and ensuring timely updates and account provisioning or deprovisioning.

Moreover, Puppet plays a vital role in establishing communication between the master server and other computers, guaranteeing access to up-to-date files. It is also commonly integrated with other open-source tools to automate virtual machines. Furthermore, users have found value in Puppet for solving business problems and supporting open-source software.

Overall, Puppet has proven to be a valuable asset for organizations looking to automate and streamline their operations. Its wide range of use cases, from maintaining configuration to deploying and managing systems, make it a powerful tool for various industries.

Reliable mechanism for deploying infrastructure-as-code: Users have found Puppet to be a dependable solution for deploying infrastructure-as-code, particularly when integrated with source control platforms like Git. Several reviewers have mentioned that it ensures system stability and uptime by effectively managing configuration drift.

Valuable asset for transitioning to DevOps: Puppet is highly regarded as a valuable tool for teams embracing DevOps practices. It empowers development teams to take ownership of their assets and automates repetitive tasks. This streamlines system management and simplifies complex operations.

Seamless integration with other community projects: Many users appreciate Puppet's seamless integration capabilities with various community/open-source projects such as Cobbler and Foreman. This integration enhances its ability to automate software installations and configure software post-installation effectively.

Confusing Execution of Actions: Some users have found the execution of actions in Puppet to be confusing, particularly when it comes to declaring the order of execution for tasks. This has caused difficulties in understanding and managing the workflow within Puppet.

Difficulty with Parallel Execution: Several users have expressed challenges in executing commands across multiple hosts in parallel, which they found convenient in Chef's knife command. The absence of this feature in Puppet has hindered their ability to efficiently manage and control large-scale deployments.

Limitations on Language and Integration: Users have mentioned limitations with Puppet's language and integration capabilities. They have experienced issues with the lack of support for inline Ruby, making it difficult to pull data from a database and incorporate it into a manifest effectively. Additionally, some users feel that implementing Puppet requires a significant shift in thinking and procedures as it may not fit well with existing infrastructure.

Based on user reviews, there are three common recommendations for Puppet. First, users advise utilizing Puppet Enterprise and consulting professional services for installation to ensure a smoother setup process and access to expert guidance. Second, it is highly recommended to get trained in Puppet and attend the Puppetize Live conference to gain a deeper understanding of the tool and stay updated with the latest developments. Lastly, users suggest exploring the Puppet Forge for pre-built modules and resources, as this library of modules can significantly enhance automation capabilities and simplify complex tasks. By following these recommendations, users can maximize their experience with Puppet and leverage its benefits effectively.

Attribute Ratings

Reviews

(1-12 of 12)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
Incentivized
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 follows the push method for sending configs to the end server. So all changes have to be pushed to all of your fleets manually. Puppet's agent will pull the config straight from the code repo so you just need to write something in your repo and puppet will pull it and do the tasks. That was the model that we actually needed. Both these products are competitive when it comes to pricing. But if our use case was different we would have gone with Ansible instead of Puppet.
Alan-Michael Barnes | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Puppet was selected before I joined the team, had it been my choice I would have much rather went with Chef as it has the ability to do things that Puppet has not yet added to their system such a the ability to quickly query what host currently are allowing puppet to maintain their files or the ability to run remote commands without having to include it in a manifest like Chef does with the knife command.

Salt allows you to do similar things to the knife command that is included with Chef, and also allows you to transfer files quickly to multiple host at once with a short simple command.
Colby Shores | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We have used SaltStack by proxy of utilizing Ceph since it uses SaltStack to automate configuration changes to it's cluster. I found it easy to use however extremely limiting when it comes to scale as its not a proper language with a central data store like Hiera. We plan to explore it again for a smaller project, however it isn't on the horizon to unseat Puppet for our primary infrastructure.
We have used Docker as well and quite frankly, it is not ready for prime time in terms of its networking. It seems great for system consolidation and exposed ports from its NAT can be run through reverse proxy to the internet. We have decided to wait until they are able to include proper static ip assignment. Finally, Docker like SaltStack, is great for smaller static configurations but not an ever changing infrastructure that relies on variables. Hiera is the main difference here.

Charles Inglese | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Chef
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.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
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 systems automation as it has a number of third party tools that wrap around it and expand what is possible.
Return to navigation