IT Central Station is now PeerSpot: Here's why

Puppet Enterprise OverviewUNIXBusinessApplication

Puppet Enterprise is #9 ranked solution in top Configuration Management tools. PeerSpot users give Puppet Enterprise an average rating of 8 out of 10. Puppet Enterprise is most commonly compared to Microsoft Endpoint Configuration Manager: Puppet Enterprise vs Microsoft Endpoint Configuration Manager. Puppet Enterprise is popular among the large enterprise segment, accounting for 72% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 19% of all views.
Buyer's Guide

Download the Configuration Management Buyer's Guide including reviews and more. Updated: May 2022

What is Puppet Enterprise?

Puppet Data Center Automation helps sysadmins automate configuration and management of machines and the software running on them. With our software, businesses can make rapid, repeatable changes and automatically enforce the consistency of systems and devices, across physical and virtual machines, on prem or in the cloud.

Puppet Enterprise was previously known as Puppet.

Puppet Enterprise Customers

Los Alamos National Laboratory, GitHub, IP Commerce, Cedexis, Spiceworks, Server Density, Swisstopo, Chockstone, Constant Contact, NICS, Citrix

Puppet Enterprise Video

Archived Puppet Enterprise Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
FernandoDe Los Rios - PeerSpot reviewer
Co-Founder and Consulting Engineer at a tech services company with 1-10 employees
Real User
It has reduced the time of production changes or environment changes.
Pros and Cons
  • "The main purpose for this automation tool would be: deploying, controlling, ordering change for the system and IT Infrastructure."
  • "Puppet Enterprise has reduced the time of production changes or environment changes."
  • "At the beginning the initial setup was kind of complex."

What is our primary use case?

I think deploying computer direction changes over production environments. The main purpose for this automation tool would be: Deploying Controlling Ordering Change for the System IT Infrastructure

How has it helped my organization?

Puppet Enterprise has reduced the time of production changes or environment changes. It is reducing the time that the engineers spend applying changes of our infrastructure. They set it all up, the next environment, and after they have been tested, when they have to promote a change, they just apply it, and it's turned on on many of hundreds of open sub-ports. To do it manually, reducing the operative time, is a really big part. I think that's the most valuable thing, because your engineers use their time with creative things, visionary things, not doing repetitive tasks.

What is most valuable?

There are two kind of Puppets: Enterprise and Open Source. So, I use Puppet Enterprise, it's helped promote the console and the recording, the reading, controlling, the checking of managed change and putting the things back together. I like it as the main. I can be relaxed, knowing that everything is in the state that it should be without taking many steps to find out how and to fix the things where there were changes properly ensures that. It saves us time, we can apply patches through Windows servers, with our tools. But, with Puppet, it can save us approximately 38 hours a month.

What needs improvement?

We are constantly improving new features, like deploying. But also, I think that they're very strange. It is how the community contributes with the models that they have in Puppet first. But it's a continuous improvement process. We are always discovering new things.
Buyer's Guide
Configuration Management
May 2022
Find out what your peers are saying about Puppet, Microsoft, BMC and others in Configuration Management. Updated: May 2022.
607,127 professionals have used our research since 2012.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

No. I haven't had any issue with the stability of the product.

What do I think about the scalability of the solution?

Well, if you are going bigger, you need to have more master servers and perform a low balancing from the servers. Also, yes, I feel like the kind of example, there's a limit of nodes that can be managed from one server. So I don't remember exactly how many. But if you need to add more nodes, you need to deploy another server into a trust relationship. Then you can deploy more nodes. I've had no issues with that. I haven't gone too big. So I'm only working with one master.

How are customer service and support?

You always find an obstacle, but you to give the feedback to them. Then, they can guide you through this to fix things that can help you to get your goals.

How was the initial setup?

Well at the beginning it was kind of complex. Because you had a lack of knowledge. So we would have to read a lot. Test many things, the configuration. After training, we saw things more clearly. We got to change the approach when they were working on. But no, it wasn't very complex. There's a lot of knowledge that you need to read in the documentation. There were no issues if someone with experience pitched the things together.  It was a learning curve. Not too hard. It's more like a not too high, not too low. It was a small learning curve.

What was our ROI?

Well I'm trying to do my job to grow the community around here. Even in Santo Domingo, Dominican Republic, where we recently deployed a project using puppet. The system manager, the assistant system manager right now is being pain when applying changes between environments. Tried creating a folder in 20 servers, for example.  I'm trying to create a community. More people know about the same, they can share experience and work together. This is part of the mantra we live by. I think that this thing is nice, these things can help you to get your goals quicker, to get these things managed in the proper way, to free up your time to use it in a more productive way.

What's my experience with pricing, setup cost, and licensing?

I think that they can only imagine $120 for node. I think it's not expensive for me, from my perspective because of what you gain and all the balances I think it will cost more than that. If you are going bigger, the licensing stuff can be doable, but I think that you can manage in the license in all the high volumes. From my perspective, I think it's not expensive. I think it's fair.

What other advice do I have?

I was trying to manage some drops raspberry pi from a Puppet master server. I wasn't able to reach that goal because there is no urgency for raspberry pi. I think I can block it, because you can use raspberry pi to manage many automation things. Many things from an IOT. I found that a couple of years ago, and I stopped playing with that. When you're using the console, it is user friendly. When you have to go down to the folders and the configuring or creating or writing code, you have to use your text editor and get down into the code. So, when everything is already configured and the models are deployed and tested, and you're pretty sure that everything's working fine, you can create a configuration, create your environment groups deploy the changes, go around the changes, using the console, the web console and it works pretty easily.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Technical Consultant at Atgen Software Solutions LLP
Consultant
It provides deployment solutions for infrastructure and applications. Setup is easy.

What is most valuable?

Puppet3 and 4 series provides optimum deployment solutions for infrastructure and applications.

How has it helped my organization?

This product has vastly increased our company’s release management and product stability functionalities.

What needs improvement?

We would like Puppet to add more integration for applications.

For how long have I used the solution?

I have used this product for 7+ years.

What was my experience with deployment of the solution?

Need to align with Agent Less Setup.

What do I think about the stability of the solution?

I have not encountered any issues with stability.

What do I think about the scalability of the solution?

I have not encountered any issues with scalability.

How is customer service and technical support?

We are highly impressed with their technical support and I would give it a 9 out of 10 rating.

How was the initial setup?

I found the setup to be quite simple and easy.

What about the implementation team?

Implement through vendor as special skills required.

What's my experience with pricing, setup cost, and licensing?

This solution supports more of agent based work.

Which other solutions did I evaluate?

Before choosing this product, I evaluated a lot of options.

What other advice do I have?

I would recommend to make use of outsourced software solutions such as Atgen for ensuring a stable setup process.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Configuration Management
May 2022
Find out what your peers are saying about Puppet, Microsoft, BMC and others in Configuration Management. Updated: May 2022.
607,127 professionals have used our research since 2012.
PeerSpot user
Principal at a tech company with 51-200 employees
Real User
Helpful support for the enterprise version.

What is most valuable?

Declarative nature of Puppet with its hub spoke architecture for automation using agents is the best feature.

How has it helped my organization?

All of the infrastructure patching and provisioning was done using Puppet.

What needs improvement?

It needs GUI based automation. There is way too much command line work involved.

Puppet is mainly command line tool with most of the scripts created through declaration. I was hoping they allow creation and deployment of these scripts through GUI based interface. In fact, if possible, they should allow deployment of all of the management infrastructure and agents deployment through process center like mechanism

For how long have I used the solution?

2 years.

What was my experience with deployment of the solution?

None.

What do I think about the stability of the solution?

No problems.

What do I think about the scalability of the solution?

No problems.

How are customer service and technical support?

Customer Service:

With the community version, the support is very sketchy. Once we bought into the enterprise version I found it very helpful. In fact, we developed very strong relationships with Puppet folks

Technical Support:

Excellent.

Which solution did I use previously and why did I switch?

I am now using Ansible and it's also a very good product. It easier to use than Puppet.

How was the initial setup?

No. It needed management infrastructure and needed HW procurement.

What about the implementation team?

Vendor Team. Expertise was top notch.

What was our ROI?

Not measured. Use of Puppet was part of larger cloud agnostic IaaS provisioning project for the enterprise. Return on IaaS project was breaking even in the same year with deployment of 500 VM servers with 3 tier app stack. Annual ROI from savings thereafter was to the tune of 60-80%

Which other solutions did I evaluate?

We looked at Chef and Salt.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user2652 - PeerSpot reviewer
Project Manager at a non-tech company with 10,001+ employees
Vendor
Popular
An advanced automation tool for centralized management

Valuable Features:

The valuable features I found are installing packages remotely and pushing files from a centralized server. Also, we can create users and monitor services remotely.

Improvements to My Organization:

We used to have lot of issues related to sudo rights on server. Now, we have centralized sudo file managed by puppet on a centralized linux server. So, any of user requests for addition or removal of sudo access, we make changes on puppet master for specific requested node and changes get pushed to puppet client on next cycle.

Room for Improvement:

The features I used so far are quite interesting and helpful.

Use of Solution:

I have been using Puppet for one year now.

Deployment Issues:

There were no issues encountered during deployment

Initial Setup:

The initial setup was quite straightforward. I reviewed some of the videos on YouTube and they helped a lot for implementation.

Implementation Team:

We implemented it in-house.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user7542 - PeerSpot reviewer
Director of Operations at a tech vendor with 51-200 employees
Vendor
Internal IT Automation With Puppet

When your company’s growing like a bean stalk on steroids (and weight gain supplements) and you live by Lean principles and practice JIT operations, you need to figure out how to efficiently manage a rapidly growing staff, and the IT infrastructure that comes with it, using a small, capable team of tech ops engineers.

A lot of ops people are rockstars when it comes to automating their production, testing, and dev environments and customer facing infrastructure, and the Conductor team is certainly in that category. But sitting in a standup (yes, sitting, legs were tired) a few months ago, we had this update from Ryan (the engineer who runs our internal IT):

Ryan: “Yesterday I provisioned two machines for new hires. Today I have some more to do.”

Me: “How many are you doing today?”

Ryan: “Two.”

Me: “What about tomorrow?”

Ryan: “Two.”

Me: “And the rest of the week?”

Ryan: “Two, two, and two.”

If you’ve ever managed or worked in a help desk, IT service bureau, or NOC, this should sound familiar. We had 10 new machines to provision that week, and one guy to do them, two per day. Quick math can tell you why this moved my hairline back a millimeter or two:

  • Ryan can provision 2 computers a day (1 machine every 4 hours).
  • We need to provision 10 computers a week.
  • Ryan was our only internal IT resource at the time who could do the work. He was also responsible for all of our other internal systems.

10 computers x 4 hours per computer = 40 hours of work

40 hour work week40 hours of work = 0 hours of time to deal with the rest of the internal service requests

0 hours spent on service requests per week = 0 satisfied, productive, fellow employees who made those requests in the first place.

This was an extreme, but if this continued, we would be saturated: not able to cover any of the other, business-critical, internal IT services we provide, and one out-of-band request away from missing our OLAs (Operational Level Agreements). Hiring wasn’t going to slow, and we had to find a way to keep up with our normal ops work and still support the high rate of growth we were seeing.

Everyone in the meeting (almost at once): Hey, why don’t we just automate it?

The answer to the capacity problem came in the form of automation, and automation came in the form of two easy to use, reliable, and proven technologies that many ops engineers use and love already: Puppet and The Foreman.

The Foreman is a complete lifecycle management tool for physical and virtual servers.1

Puppet Open Source is a flexible, customizable framework available under the Apache 2.0 license designed to help system administrators automate the many repetitive tasks they regularly perform.2

The idea was to stop looking at these purely as server management tools, and to apply the same configuration management principles to our employees computers. This gave us a number of advantages:

  1. Provisioning new employee machines went from a 4 hour process of manually installing various packages and configurations to a 5 minutes process of registering the machine with Foreman and triggering a Puppet run.
  2. Rolling out upgrades across the company became a fully automated process, requiring us only to upload a Puppet module on the Puppet master server and wait for or force Puppet runs on the client machines.
  3. Configuration compliance became a non-issue, since we could manage all sensitive configurations with Puppet modules.
  4. Detailed reporting on the configuration of all employee machines allowed us to troubleshoot issues quickly, and sometimes diagnose and resolve them before the user was even aware of the problem.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
sumodirjo - PeerSpot reviewer
Senior Site Infrastructure Engineer at Kurungsiku
Real User
Top 20
Help you manage your servers so you could sleep better

Valuable Features:

I work with puppet several weeks back, helping a client using puppet enterprise to manage Windows servers. Puppet is solid, the enterprise version have installer wizard that will also install all puppet requirements like MySQL. Puppet could be used in the simplest way. Only one file manifest, or you could split a file per host or you can follow the best practice where you create classes and import that class on a manifest. You can even extend your manifest with ruby. Puppet support Linux, Windows and UNIX. Puppet documentation is also good.

Room for Improvement:

Puppet has steep learning curve so you need to spend some time before you can use puppet on your daily. If you only manage a small number of servers the time to create manifest might be longer than you create, edit and copy configuration manually to each server, but if you’re looking for long-term solution of course this is worth doing. Even that the documentation is good, I can’t find enough manifest sample for some basic usage, have to Google a lot, bumping from one blog to another blog. Puppet Enterprise give you limit to manage only 10 machine, but if you need to manage more machine but don’t want to spend money you can use puppet open source.

Other Advice:

Good tools to automate your servers, the time and effort to learn writing manifest is quiet high but it's worth on the long run
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Configuration Management Report and find out what your peers are saying about Puppet, Microsoft, BMC, and more!
Updated: May 2022
Product Categories
Configuration Management
Buyer's Guide
Download our free Configuration Management Report and find out what your peers are saying about Puppet, Microsoft, BMC, and more!