Ansible Other Solutions Considered

Eric Greene
Senior DevOps Engineer at a tech vendor with 201-500 employees
I was a very big Bash script guy years ago on automating deployments. Then, I moved into Puppet. I did Puppet for a few years, and was very involved in the community there as well. After that, I moved over to SaltStack. The design of SaltStack was a bit complicated, as it felt very split brain. So, I did that for about six months, then I decided to look more at Ansible, which I dabbled with for about two years before I started using it. It was a little complicated to use as the action system was weird, but they have over come a lot of those issues. Now, the Ansible modules are simple and easy to use, so I moved to Ansible and haven't changed since then. View full review »
Eric Spencer
Network Engineer at a legal firm with 1,001-5,000 employees
I did some training and I've messed around with Terraform. They do have providers for Palo, specifically. But in network, I'm dealing with mostly bare metal devices. And Terraform, that's just not what it's meant to do. I was trying to see if I could do some things with it, but it's not the right solution. Some of my peers dealing with servers, they use a lot of Terraform because they can say, "Well, we have an environment that needs to be four to eight servers. Create the Terraform configuration and the TF files and TFR files and just let it do its thing." But I can't really do that with 1,500 physical devices that already exist. View full review »
Mohamed Ibrahim
Senior DevOps at RubiconMD
We considered Chef and Puppet, which are very similar to Ansible. However, they have a more Ruby-based programming language. Therefore, it takes more time to learn and incorporate into a company. Ansible is easier for everyone to understand what is going on without actually knowing the programming language. We chose Ansible for simplicity. Ansible is easy to set up, then get up and running in about a day or so. With Chef, I would have had to sit there and learn it, so the time constraints didn't really work out. View full review »
Learn what your peers think about Ansible. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
419,214 professionals have used our research since 2012.
Clarence Mills
System Engineer at a tech vendor
I've used Salt and I've used Puppet. The reason I like Ansible is, first, the coding of it is very straightforward, it's very human-readable. I'm also on a contract, and I can clearly iterate and bring people up to speed very quickly on writing a Playbook, compared with writing up a Puppet manifest or a Salt script. View full review »
Chris Smolen
Senior Network Engineer at ePlus Technology
I have looked at Puppet because they are now trying to get into the network space, but it is not that easy. The feeling of the product is not as good. View full review »
Senior Data Architect at Crunchy data
I looked at Puppet and Chef. They are good tools, but there is a language barrier. I've been using Python for more than six years. Using Ansible was a piece of cake for me. Also, Puppet requests an agent. As with many places that I looked at it, it was a no-go if you have to install agent. We have a client system and need to install a client to configure or maintain our systems, so it is a no-go with an agent. With Ansible, it can remotely execute tasks and do its job. View full review »
Marek Jeerzejewicz
Senior Director Network Security at Oracle Corporation
We do use Puppet and Chef in some other areas. However, Ansible is our dominant platform. View full review »
Ahmad Bukhari
Senior Security Engineer at Mindpoint
Puppet and Chef are cool, and have been in the game much longer, but Ansible is way better. View full review »
Shashank Jha
Senior Software Developer at HCL Technologies
I researched with other tools, but I still chose Ansible. One reason, it was agentless. With other tools, I had to install agents. Ansible has a big plus factor being agentless. View full review »
Learn what your peers think about Ansible. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
419,214 professionals have used our research since 2012.