Perforce Puppet Reviews

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

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.

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.

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.

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

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.

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.

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.

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.

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.

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.