Ansible Reviews & Product Details


What is Ansible?

Ansible is a simple way to automate apps and infrastructure. Application Deployment + Configuration Management + Continuous Delivery.

Write a Review

Ansible Screenshots


Ansible Profile Details

Ansible Profile Details

Vendor
Red Hat
Description
At Red Hat, they connect an innovative community of customers, partners, and contributors to deliver an open source stack of trusted, high-performing technologies that solve business problems.
Company Website
Year Founded
1993
Total Revenue (USD mm)
2,920
HQ Location
Raleigh, NC
Ownership
NYSE: RHT
LinkedIn® Page
www.linkedin.com
Employees on LinkedIn®
12,189
Twitter
@RedHatSoftware
Twitter Followers
15,760
Show moreShow fewer

Companies Using Ansible

Cisco
Rackspace
Twitter
PayPal
Capital One
New Relic
Sabre
Electronic Arts (EA)
Juniper Networks
Weight Watchers
Splunk
Okta

Ansible Reviews

Filter Reviews
Filter Reviews
Sort by
Ratings
Company Size
User Role
For Category
All Industries
Write a Review
1-50 of 65 total Ansible reviews

Ansible Reviews

Write a Review
Filter By
Connections
Show reviews that mention
1-50 of 65 total Ansible reviews
Copy Review URL
DevOps Principal Architect
Mid-Market
(201-500 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"The Swiss Army knife of automation scripting. My favorite automation tool."

What do you like best?

- Great flexibility, with proper code organization you can automate any process you want at any complexity!

- Ansible is very easy to setup, being an agent-less tool. You can get started without installing any software on the target machine where you would like to execute your automation

- Great abstractions: roles (modules), inventory hosts and groups, facts (node information) and group-level as well as host-level variables. You can implement very complex automations in a very clean approach with Ansible abstractions.

- A lot of modules available at your disposal. From simple file copying, to templated files, to services and packages management. You will probably forget bash syntax after using Ansible for awhile. Well, you can also use bash to accomplish tasks that do not have modules for.

What do you dislike?

There are very little cons, but here are some cons that by design:

- Due to lack of centralized server, you cannot orchestrate automations that span multiple nodes asynchronously. You can still run a playbook against all nodes of the cluster, but if there are inter-dependencies, then all hosts must be included in the playbook and you have to implement some logic to resolve those dependencies. By contract, when using a centralized tool like Chef, you can fetch information from centralized data structures which can be populated asynchronously.

- Also due to simplicity, Ansible does not handle playbook versioning, it's something that you have to implement on your own.

What problems are you solving with the product? What benefits have you realized?

Complex automations. It greatly allowed us to implement very complex automations in clean, reusable manner.

Copy Review URL
Software configuration engineer
Information Technology and Services
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"If your environment to manage is Linux, Ansible should be your election."

What do you like best?

Ansible born in Linux to manage Linux so the features are designed to be smoothly and very easy to do, for a sysadmin understand how works and start using is very easy, and for developers is easy to manage infrastructure with limited knowledge or background.

What do you dislike?

Support for windows environments are still limited, is better than previous versions but there is still a lot of work to do.

Recommendations to others considering the product:

If your environment is only Linux or cloud based Ansible is your best option, if you have Windows servers you will need check if your needs can be covered by Ansible.

The initial setup is simple and learn to work with it is very simple for sysadmins and even for developers.

If you can architect your solution with Galaxy should be great, or with Ansible standalone should be enough for most environments.

What problems are you solving with the product? What benefits have you realized?

I'm using Ansible to automate cloud deploys for Openstack infrastructure, and for the continuous integration/continuous delivery process (We are using Zuul and is tied to Ansible)

Copy Review URL
Senior Technology Architect
Telecommunications
Enterprise
(1001-5000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Automation for SysAdmins"

What do you like best?

Ansible is an amazing tool who allows to automating SysAdmin tasks like big deployment of the same instances or managing updates. All this : without physically accessing the machine and all is logged so it remains ISO 20K compliant !

What do you dislike?

There is a learning curve and you need to understand Yaml to write playbooks. But actually, this is not too complex and the wiki website is well documented. The community is very big.

Recommendations to others considering the product:

Don't be afraid to learn new products, this one really really worth your time investment. It is free, open source and community drive OR you can buy subscription and get support from Red Hat directly. There is UI called Tower, but if you don't absolutely need it, avoid it.

What problems are you solving with the product? What benefits have you realized?

Deployment at scale of complex environment with audit logs.

Copy Review URL
Software & Network Systems Engineer
Small-Business
(11-50 employees)
Validated Reviewer
Review Source
Copy Review URL

"Revolutionary manager for groups of servers"

What do you like best?

The simplicity of commands to manage a full complex group of servers. It's really easy to see where they are alive or not (via a ping play, for example). With playbooks, you automate the building. What I like the most is that you can use it along Docker, and even Vagrant. At our company, in the next software version we will deploy, we will be using Ansible due to its simplicity. We've already built some of the playbooks

What do you dislike?

Really, the only thing I would like is Ansible Tower to be free. But well, not everything is possible!

Recommendations to others considering the product:

Do not fear, I am still facing superiors to change to Ansible because they are too only-bash-basic-commands and build-everything-on-bash.

What problems are you solving with the product? What benefits have you realized?

We are managing a group of servers that need to be deployed and updated. The software we are releasing has some modules that change, and we need them updated whenever the client calls or via planned updates. The thing is that when something is failing in a client, we find what's causing the problem, and then replicate in the rest of the servers. It's simply astonishing.

Copy Review URL
Infrastructure Engineer
Information Technology and Services
Enterprise
(10,001+ employees)
Validated Reviewer
Review Source
Copy Review URL

"Great system automation"

What do you like best?

Ansible is a great tool for managing servers, especially for tasks that would traditionally fall under the umbrella of system administration. The ability to manage servers without installing clients (it uses SSH) removes a huge barrier to entry and allows you to use it to manage a large number of devices.

What do you dislike?

There is lots of documentation, but it lacks a good API, in the sense of having a set of documents that tell you how all the inner-workings operate. There are many examples, but it can be difficult to find a comprehensive list of all the different operations that Ansible uses, and how things work. This makes the inner-workings feel like a black box, and sometimes you have to resort to a try-this-and-see-what-happens approach to getting it to do what you want. Once you get it running, especially after you've used it more and "get" how it works, it can be pretty frustrating.

Recommendations to others considering the product:

Spend some time reading through documentation, and looking through other people's code (Github, et al) to get an understanding of how it works and what you can do with it (and how). This might make it easier to get up and running and to make sure you can do what you want with it.

What problems are you solving with the product? What benefits have you realized?

Managing large sets of servers in a programmatic way that is version-controlled, and easily managed both by people who are code-knowledgable and those who are not (Ansible uses yaml, which essentially looks like a todo list)

Copy Review URL
Bitcoin Trader
Utilities
Validated Reviewer
Review Source
Copy Review URL

"Easy to use"

What do you like best?

The Ansible software can upgrade web servers at one time at a time, and in its upgrade, it can remove the current web server from load balancing and disable it in its Nagios monitoring system. So, in a short time, I can manage complex tasks with ease.

What do you dislike?

This tool can be installed and used on some Linux distributions like CentOS, Debian and Redhat Enterprise.

Recommendations to others considering the product:

Ansible is a powerful and efficient open source tool for managing and configuring systems, extending programs, automating and synchronizing tasks, and more.

What problems are you solving with the product? What benefits have you realized?

Compared to other automation tools such as Chef or Puppet, it is not necessary to install the Agent on nodes, and all nodes will be managed by a control machine via SSH.

Copy Review URL
UI
Enterprise
(1001-5000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Automation... Ansible makes it a breeze"

What do you like best?

Easy to learn, fast to implement, no need to have various agents installed in your remote servers - a simple SSH connection can serve you, installation is a breeze - pip/apt/brew - any package manager of your choice, though Ansible itself is written in python, you don't need to learn python to use Ansible, uses human-friendly yaml syntax (eye-candy), easily integrates with most cloud infra providers, ever growing modules, easy management of tasks (modules), guarantees idempotency

What do you dislike?

Ansible is not yet mature to accept python3

Ansible uses Jinja2 as a part of its templating system. Hence, not knowing the jinja DSL can hurt you back

Recommendations to others considering the product:

Each of the tools have been created to solve a different type of business need. What Ansible had to offer us is different from what it has to offer other businesses. Hence, it is advisable to other users to first know the business problem they are trying to solve and assess how Ansible fits in that place.

Similarly, if you think you need to learn python to use Ansible, don't be discouraged, you don't need to. Well, it helps to extend modules if you do know python fundamentals.

What problems are you solving with the product? What benefits have you realized?

deployment

orchestration

automation

configuration management

patch management

Copy Review URL
Senior Cloud Consultant
Information Technology and Services
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Easy to get going, advanced enough to do what you need to do"

What do you like best?

Ansible is easy to get into, it has a simplistic configuration and allows for a huge variety of integrations with other services.

What do you dislike?

The major downside is when you need something that is not officially supported. You'll get on galaxy and look for a 3rd party plugin. Some of those are great, but not all.

What problems are you solving with the product? What benefits have you realized?

Previously we used webmin to manage our servers, it was a mess. These days we use Ansible as Configuration Management and are looking to expand its usage into builds and deployment.

Copy Review URL
UI
Mid-Market
(201-500 employees)
Validated Reviewer
Review Source
Copy Review URL

"An awesome tool for automated deployment"

What do you like best?

Ansible is a very easy to use tool. it has modules with almost everything eg. Shell, MySQL. Etc. It is YAML based and very easy to use. It only takes 3hours to learna and start writing your playbooks.

What do you dislike?

There is nothing which I dislike about ansible. May be it can improve on it's documentation a bit and develop a UI for better tooling

Recommendations to others considering the product:

I think if you are looking to automat your deployment process, you should definitely look into ansible. There are other tools as well , but it is a very simple took based on YAML. And it reduces the amount of coding to a great extent. Just use the syntax as mentioned in the documentation and you are good

What problems are you solving with the product? What benefits have you realized?

Automated deployment plus continuous integration and continuous deployment capabilities. Benefits are pretty visibly in terms of ease of use, simplicity, fast performance, compatibility with other frameworks.

Copy Review URL
DevOps Engineer
Online Media
Mid-Market
(501-1000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Great for configuring Mesos cluster nodes"

What do you like best?

- no agent required, as long as you can establish SSH - it works

- flexibility to run with a dedicated server or with workstations

- allows separation of leader and agent tasks into separate .yaml files that can be called using conditional checks in the main.yaml (control file)

- very readable and powerful template engine

What do you dislike?

- DNS lookup facility has a python library dependency

- the DSL to use dig lookup to do a reverse lookup is not very readable; it's more readable and reliable to local-exec dig

- need to maintain an inventory of your machines

Recommendations to others considering the product:

Ansible works really well for cattle-type deploys meaning when you need automation/configuration management to build up infrastructure that will be torn down and rebuilt when updating. If you intend on your CF to converge your configs, probably Chef or Puppet works better. In our use case when we upgrade or run into problems, it's quicker for us to destroy the instances in question and reprovision/reconfigure. For this use-case, Ansible works really well.

What problems are you solving with the product? What benefits have you realized?

We have been able to automate the configuration of our Mesos cluster nodes. Prior to this, configuring Mesos nodes was very manual and error-prone. Now we can provision the nodes with Terraform and configure them in a few minutes rather than going through hours of configuration.

Copy Review URL
Ingénieur d'affaires
Computer Software
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Simplest configuration management tool available out there"

What do you like best?

Ansible is an open source solution that makes configuring infrastructures an easy task for sysadmins. In the contrary to other configuration management tools, Ansible is very simple to get started with and it lowers the entry barrier to automation, all you need to write playbooks is a text editor. One of the powerful features of Ansible is that it is agent-less, which means there is no need to install any software on remote systems (especially your client's systems) in order to automate a task (installing a software stack) on these machines. Also, Ansible relies on the SSH protocol while other automation tools use their own protocols that may need special firewall ports to be opened. Furthermore, Ansible can be easily used with tools like Vagrant to automate the provisioning of development environments on local machine.

What do you dislike?

The main drawback is the absence of an open source graphical interface for Ansible that make it easy to monitor the entire inventory. Ansible only provide an command line utility and the only GUI solution available seems to be Ansible Tower which is an enterprise solution. Ansible was recently bought by RedHat so this may raise questions on the direction the project will take in future.

Recommendations to others considering the product:

Ansible has excellent performance, it has no need for installing any agents on remote systems. it's based on python which is a well known language for scripting especially among the sysadmin community. Ansible is the way to go if these properties fit in your day-to-day requirements.

What problems are you solving with the product? What benefits have you realized?

We switched from Chef into Ansible to exclusively automating the provisioning of platforms on AWS (and other Cloud providers) and configuring application stacks for our clients. The stack range from RoR (Ruby on Rails) to Django web applications; to database management and clustering. The switching wasn't very painful, and Ansible helped us quickly writing new automation tasks. Furthermore, we gained a lot from the ability to use Vagrant along with Ansible in order to replicate production environment into the developer's machines and having a huge boost in terms of productivity, detecting bugs and fixing them quickly.

Copy Review URL
Network Engineer
Internet
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Excellent devops tool"

What do you like best?

Ansible is extremely flexible with dozens if not hundreds of modules, including powershell

What do you dislike?

The learning curve is a little steep if you’ve never used a tool like this before, but it’s something you could pick up over a day or two

Recommendations to others considering the product:

Take a good couple days to evaluate all the processes and scripts you run on a regular basis. Chances are they can all be setup in Ansible

What problems are you solving with the product? What benefits have you realized?

Weekly and daily repetitive tasks that usually take several hours now take us about 5 minutes

Copy Review URL
infra solution engineer
Mid-Market
(51-200 employees)
Validated Reviewer
Review Source
Copy Review URL
Business partner of the vendor or vendor's competitor, not included in G2 scores.

"Simple IT Automation Tool"

What do you like best?

It easy to understand command line interface and it is a less number of commands in tool.easy to write a playbook without code knowledge also.it is simple IT automation Tool and it is open source tool.it manages number of hosts at a time.

What do you dislike?

while writing a playbook using YMAL it validates indentation.

Recommendations to others considering the product:

it takes less time to implement in your organization .you can get all the documentation to learn about Ansible.

What problems are you solving with the product? What benefits have you realized?

we are using it for automation for our server configuration which saves a lot of time.

Ansible helps to make infrastructure development very Simple.

Copy Review URL
Principal System Architect
Telecommunications
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Can't live without it now that I use it - Use it for Orchestration of deployments and new buildouts"

What do you like best?

The YAML syntax is so easy that anyone can use it. No more excuses from people that they are not a coder, they can now declaratively define their infrastructure via code just by knowing YAML. It allows me to version control my infrastructure now that it is defined by code.

What do you dislike?

Sometimes the data structures available seem limiting but once you really learn the tool, it all comes into focus. The documentation can be limited for the modules but you can always read the source code as its just python and really easy to read and understand.

Recommendations to others considering the product:

Start with the community edition and see if its enough before purchasing Ansible Tower. Remember to always version control your playbooks.

What problems are you solving with the product? What benefits have you realized?

Reduce the lead times when provisioning new complex multi-tier stacks from Linux VM's to load balancer VIP's and SSL certification installations.

I also rely on Ansible for deployments of multi-tier application from my CI/CD server (Bamboo). Ansible is available on the Bamboo server so the deployment playbook gets version controlled alongside the app's source code and is executed by Bamboo/Ansible at deploy time. I also rely on Liquibase for DB schema evolution which is also executed by Ansible.

Copy Review URL
Sr. DevOps/Cloud Engineer
Computer Software
Validated Reviewer
Review Source
Copy Review URL

"Very easy to use"

What do you like best?

It is very easy to use. All you to do is write in a bunch of commands and give it an inventory file and the ansible will execute those commands on all the servers that are in the inventory file.

What do you dislike?

Ansible is push based. It is not pull based like puppet. So we may not be able to have a fixed constant environment like we have with puppet. One may make changes on one server and we may not even know that.

Recommendations to others considering the product:

I strongly recommend using this.

What problems are you solving with the product? What benefits have you realized?

Ability to do multiple tasks on multiple servers at the same time by writing a small script.

Copy Review URL
Research Intern
Higher Education
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Best tool to seamlessly manage everything in a Data center. "

What do you like best?

The best thing is that its a one stop solution to all of our needs to manage an entire data center. We can manage configurations, deploy applications and it lets multiple people to work together rather than the traditional one sysadmin to manage it all, which is also possible from the Ansible command line.

The other thing is that its open source, which lets me add feature which other can use too. The community is very active too.

What do you dislike?

There are some features which i would like to be implemented one of which is supporting Kubernetes by Google and rkt from CoreOS but I am sure that its certainly on their roadmap and they will be adding those in the near future.

Other than that I don't think there is anything which I don't like in particular. It has really reduced overhead of managing using different tools, writing scripts and managing configurations.

What problems are you solving with the product? What benefits have you realized?

We are managing a data center in a university which handles application deployment for research purposes.

Ansible is the only solution we need to do all of that, otherwise we had to use atleast a dozen of other softwares and it even would have been impossible. We don't need to write scripts anymore.

We are using SDN (Software Defined Networks) to automate network configurations on HP SDN enabled switches

Copy Review URL
II
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Configuration Management without hassle"

What do you like best?

No Agents Required

Works on top of SSH

Can reverse the methodology to pull vs push, using Ansible Pull.

Pure Ansible,

Supports Dynamic inventory

What do you dislike?

If your playbook/role gets failed, the error at the very last step, the next re-run will do all the steps all over again.

Although the ansible will be idempotent but wastes lot of time in big environment.

Can tackle this using Tags, but that needs to added at the time of creating the playbook.

Recommendations to others considering the product:

Ansible is great Config Management tool, I used the opensource version of it.

Its simply awesome, right your manifest in yml file and just deploy it.

Since there is no agent and master server concept. Your system will not have single point of failure or additional resource usage on client size. Just needs SSH thats it.

I used Ansible apart from deploying servers to collect and gather facts from remote machine and used as CMDB.

What problems are you solving with the product? What benefits have you realized?

I have used Ansible to configure my application and used it to generate the CMDB by collecting the facts generated by Ansible.

Copy Review URL
Concepteur/Développeur
Telecommunications
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Ansible is an easy to learn, extensible and has a module for everything"

What do you like best?

There is a plenty of configuration management tools that helps you automate tasks and gain in productivity. Each one has its own specific way for configuration management, with many different pros and cons.

Among these tools Ansible stand a part as an automation tool that works very well while very easily to get started with. It's killer feature is that you don't need a specific infrastructure setup, no need to deploy agents all over to get an Ansible script working. In addition, Ansible is very extensible and has a plethora of modules that you can use to deploy any software stack (ruby on rails, django, etc.) as well as provisioning infrastructure resources from many providers whether it is cloud (e.g. Amazon cloud) or on premise (e.g. openstack, vargant).

What do you dislike?

Ansible is no more independent as it was purchased by RedHat in order to make it more Enterprise friendly. Furthermore, this change may impact the choice what modules will be maintained by the core team. For instance, it more likely that the Openstack module will be more prioritised than the vagrant module or AWS module.

Also, Ansible is mostly a CLI tool with no advanced support for a graphical interface (which is the case of most of the other configuration management tools), though it has the Ansible Tower but it is an enterprise product.

Recommendations to others considering the product:

If you have to manage a large number of servers hosting a much larger number of applications, then you must start looking for an automation tool. In this case Ansible is the choice to consider, it is the easiest tool out there to learn and has many modules and writing own modules if needed is not hard (python scripts).

What problems are you solving with the product? What benefits have you realized?

I started looking for automation systems since I wrote my first bash scripts because writing bash scripts is hard and maintaining them is even harder. Furthermore, I'm not a system administrator but rather a developer and I hate to do the same thing twice. I believe (and you should too) in DRY (Don't Repeat Yourself).

Tools like Ansible are powerful as they gave a boost in productivity when it comes to handle many machines and applications with a lot of moving parts.

Copy Review URL
Army Of One
Computer Software
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Continuous Delivery with Ansible, Jenkins and Docker"

What do you like best?

Ansible is really easy to use. Its default plugins covers most of the core needs that a DevOps could use. Unlike Chef, you don't need any client on the nodes you want to manage as everything is done through SSH. This reduction in complexity helps a lot in plugin development, bug fixing and debugging.

What do you dislike?

Most of the times documentation is nice or enough but, sometimes, it's a bit tricky to understand some of the characteristics or commands of some plugins, sometimes because you need deep understanding of the things you're going to do, sometimes because description isn't perfect. You'll manage to do everything at the end.

Recommendations to others considering the product:

If you are starting in DevOps world, start with Ansible. If you have spend some time in DevOps world or you're already an expert that haven't used it yet, give it a try, I'm sure that most of the users will enjoy its simplicity and ease of use.

What problems are you solving with the product? What benefits have you realized?

Deployment of dozens of nodes at the same time. Our benefits are the development and testing of our playbooks, that are lot easier that with Chef (our previous solution) without the deployment of the Chef Server + an Chef Agent on each machine in our cluster.

Copy Review URL
Linux System Administrator & Programmer
Internet
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Effortless server configuration"

What do you like best?

I love that there is no agent to install on each server that you want to manage. Everything is done over SSH. I started writing playbooks and doing the same actions on multiple servers in minutes.

What do you dislike?

Sometimes, the documentation is a little vague. More concrete examples would be very helpful for new users. Luckily, there are some good guides online from other sources.

Recommendations to others considering the product:

Read the documentation. Almost everything is covered very well, but because it is so flexible they can't put every situation in the documentation. Search online for how others user Ansible in their environments. Search GitHub for playbooks.

What problems are you solving with the product? What benefits have you realized?

I manage ~400 servers and I needed a way to easily spin up a new VPS and install our application on it. What used to take about an hour now takes about a minute. I also use Ansible for continuous deployment. Application updates are scripted with Ansible and can be on each server almost instantly. Ansible also allowed us to keep a consistent server configuration across our business.

Copy Review URL
Co-Founder and Chief Technology Officer
Information Technology and Services
Small-Business
(2-10 employees)
Validated Reviewer
Review Source
Copy Review URL

"Really Enjoy Ansible"

What do you like best?

The syntax is very easy, I typically use YAML for all of my application configuration so I'm happy Ansible uses YAML.

It's great that I can run playbooks against servers just over SSH, I don't have to install any agents on the remote servers.

I like how everything just describes what the desired state is and it works idempotently.

We had previously worked with Chef and Puppet and Ansible by far has been the easiest for us to get up and running.

We started out with configuration generated by http://phansible.com/ which helped us get up and running quickly.

What do you dislike?

We had a developer running on Windows and we were unable to get it working. Had to jump through some hoops to get that developer onboard.

We tried using Cygwin which is what tutorials on the net suggested, but we were unable to get it to work. We were using it with Vagrant so it's possible it's an issue with Vagrant and Ansible on Windows. This developer was able to get Vagrant running with Puppet.

Recommendations to others considering the product:

Ansible has been great for us. It can be tricky if you have developers using Windows. We are a PHP shop so we found the site http://phansible.com/ to be a great asset to get a starting set of configuration.

What problems are you solving with the product? What benefits have you realized?

Initially, it was only for configuring vagrant development boxes. Recently we've started experimenting with using it to configure our VPSs. It's coming along very nicely.

Copy Review URL
Database Administrator
Information Technology and Services
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Simple and Powerful CM tool "

What do you like best?

Ansible it's the most simple and easy to use Configuration Management tool on market, it's just what we want. Playbooks are simple to write and to understand. It's soo easy to use that I could argue that an Ansible role it's like a documentation, once you read you know exactly how it operates/work.

Another top feature of Ansible it's that I don't need any agents to work, just add the public key and "boom" it's working, this is extremely useful for us since we don't need to modify anything on clients.

What do you dislike?

Ansible it's quite new so for very complicated automations you maybe find yourself building a lot of code to make it work as you need.

Recommendations to others considering the product:

If you need to automate a lot of Windows machines, don't use Ansible!

If you have a extremely heterogeneous environment, don't use Ansible!

If the two phrases above aren't true, use Ansible!

What problems are you solving with the product? What benefits have you realized?

We are building kind of a "One server sees everything". This is a "piece of cake" for Ansible because you can use features like Bastion host of Openssh. For remote servers that my controller machine can't SSH it's possible to use another host as a Proxy. We are also using it to orchestrate automation on all machines we have.

Copy Review URL
UI
Mid-Market
(201-500 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"DevOps Engineer at Refinery29"

What do you like best?

It's simple. Modules exist for nearly every task you can think of, and if there isn't one, they're easy to write in python or any other language (so long as it supports file I/O and outputting to standard out). You can even control AWS services with it, just using built-in modules. And if you're too lazy to write a module, the command and shell modules allow direct execution of commands as if you had ssh'd into the target host. Ansible is basically just a wrapper for running commands over ssh anyway.

What do you dislike?

Coming from Chef, I miss the ability to use prewritten cookbooks, or in Ansible parlance, roles. The community is not as robust as Chef's, mostly because Ansible is so much younger a project.

Recommendations to others considering the product:

Ease into it. Ansible is easy to write using just the command and shell modules, but checking to see if modules already exist will save a ton of time, and provide better reporting. Once you get the hang of writing your own modules, everything feels like it falls into place.

What problems are you solving with the product? What benefits have you realized?

We need to rapidly, consistently provision systems for development, QA, and serving our site. At Refinery29, we have Ansible scripts for (just about) every system we have.

Copy Review URL
Data Engineer
Information Technology and Services
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Ansible is so easy, it feels like cheating"

What do you like best?

The best thing about is that it's agentless, meaning it doesn't require anything running on your target instances, before provisioning them. Good old SSH is all you need.

Before switching to Ansible, I was using Puppet. When compared, Ansible just makes everything work like a breeze. No more do I have to figure out how to make the target instances communicate with my Puppetmaster *before* you can do any kind of provisioning. With Ansible your instances are provisionable from the get-go.

Other things I like about it:

- Ad-Hoc commands

- Ansible Galaxy, especially how you can retrieve roles either from the public repositories or from your private SCM repositories.

- Ansible core has a task for almost any kind of work

- Works well with CI tools and it is beneficial to add the playbooks to your deployment pipeline, so the environments are provisioned each time code is committed.

- The tasks are ideally idempotent, so it won't redo the changes if everything looks okay on the target instance. (The reason why I say 'ideally' is because it is possible for you to make tasks that are not idempotent. But it is something you should avoid.)

What do you dislike?

YAML-only syntax might not always be the most customizable. Also it has most of the *magic* running out of sight, so you have to read through the Ansible source code on purpose, if you want to know what it actually does.

What problems are you solving with the product? What benefits have you realized?

Main problem I've solved is keeping the test, dev and production environments identical.

Copy Review URL
DevOps Engineer
Defense & Space
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Best Configuration Management software available"

What do you like best?

The fact that Ansible uses SSH for transport is incredibly convenient, and the fact that Playbooks are written as YAML datastructures makes them incredibly easy to read and maintain, even for managers, who may not be technical.

Ansible puts a high stress on idempotency, meaning that you can rest easy knowing that your servers are in exactly the sate you expect them to be in, and changes will only be made if you want them to be.

Ansible is also exceptional at provisioning, not just configuration management.

What do you dislike?

Ansible Tower needs a lot of work with concurrency and high availability. Ansible Tower is priced too high for an on-prem solution. Automated tests need to be improved to reduce the occurrences of things breaking with a new release.

Recommendations to others considering the product:

Be sure to structure your roles in small, re-usable chunks and variablize everything. Explore Ansible Galaxy to find roles that may already exist for what you are trying to do.

What problems are you solving with the product? What benefits have you realized?

Provisioning and Deploying a large and complex infrastructure of over a dozen microservices in a CI/CD environment using a combination of Docker, Ansible, and Jenkins in AWS.

Ansible is far easier to use and maintain than Chef or Puppet, and is completely agentless.

Copy Review URL
GI
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Config Management for the Rest of Us"

What do you like best?

Ansible is simple:

It works with Python and uses SSH on Linux + UNIX systems. Write YAML "playbooks" and run them any platform you need. We use it on CentOS, FreeBSD, and Ubuntu - but Windows works as well.

What do we use Ansible for?

To deploy configuration to many systems, to stand up web applications we use, to backup files and data, to secure services on our servers, and much more.

Modules exist for every service or application you can think of. Would you like to manage KVM with Ansible? Can do! Want to manage your ssh keys across multiple employees? No problem!

The Ansible Galaxy site has many playbooks where you can learn by example. There are also hundreds of playbooks freely available to be forked on GitHub.

What do you dislike?

I think there's a bit of a learning curve with Ansible as far as writing the playbooks out. There's a large gap in my mind between a simple playbook that maybe configures one service or hardens a server, and a super complex playbook that can manage applications at a large scale. It takes time and planning and most importantly TESTING. We test our playbooks a lot because one variable can make a difference between a success or a disaster.

Recommendations to others considering the product:

I would read the documentation and get completely buried in everything it can do.

What problems are you solving with the product? What benefits have you realized?

We use it to stand up new servers, setup new applications, deploy a new service to more than one machine in your fleet. Can also use it to copy config files or other important things between the 'master' (even though Ansible is designed so you don't need one).

Copy Review URL
GC
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Linux Automation "

What do you like best?

I love, that Ansible is Python based and provide very flexible way to configure any part of host configuration and it is free. I've widely used Ansible to deploy and configure various application in Linux. The great benefit, that Ansible does not require any agent and use ssh (you have to sort SSL related query on PRD). One more great advantage is that playbooks has defined structure and there are tons of addons in galaxy source.

What do you dislike?

As Ansible is Python based, it is very much sensitive to code. So you should have exact number of spaces in each line or Ansible will fail.

Recommendations to others considering the product:

test playbooks prior execution on using available feature

What problems are you solving with the product? What benefits have you realized?

Environment deployment Automation, preparing different changes on installed software, using templates for configures.

With Ansible we can follow Configuration as a Code conception and made our changes more predictable and easy to verify.

Copy Review URL
Junior Rails Developer
Information Technology and Services
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Amazing provisioning tool!"

What do you like best?

I really like speed of writing: simple yaml script and my machine up and ready to work in matter of 10-15 minutes. I also recommend ansible to my colleagues for their own software configuration

What do you dislike?

python 2 <<< sometimes causes unexpected errors

Recommendations to others considering the product:

Sometime you do the right thing: it is the first time when you start learning ansible. Then you change the way you work and start enhance the way your team work. Everything will change for the better and that's great you can do more in less time.

What problems are you solving with the product? What benefits have you realized?

Ansible help me prepare my machine and machine of other devs to work in matter of minutes, so we can start working on the our customers problems. Currently I work in Syndicode LLC. We offer Ruby on Rails solutions for various online business, but primary E-commerce and GPS-monitoring

Copy Review URL
Software Engineer
Internet
Mid-Market
(501-1000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Good for Configuration Management"

What do you like best?

Ansible provides a simple way to perform distributed server management, and it's quite easy to maintain configuration for a group of servers. Overall, my favorite portions are the simplicity and efficiency, especially that it does not require a dedicated server to act as the host for configuration.

What do you dislike?

I've only used it for a few servers, and I'm not entirely sure how it would perform in larger-scale implementations, with hundreds or thousands of servers with widely varying roles.

Recommendations to others considering the product:

Gather requirements beforehand.

What problems are you solving with the product? What benefits have you realized?

Configuration of multiple servers and keeping all configuration inside a git repo. The fact that it allows me to easily and quickly set up new servers is extremely valuable, as well.

Copy Review URL
Software Developer
Food & Beverages
Mid-Market
(51-200 employees)
Validated Reviewer
Review Source