"Being a game-changer in configuration management software is what has made Ansible so popular and widespread. Much of IT is based on SSH direct connectivity with a need for running infrastructure in an agentless way, and that has been a big plus. SSH has become a great security standard for managing servers. The whole thing has really become an out-of-the-box solution for managing a Unix estate."
"Ansible is agentless. So, we don't need to set up any agent into the computer we are interacting with. The only prerequisite is that the host with which we are going to interact must have the Python interpreter installed on it. We can connect to a host and do our configuration by using Ansible."
"One of the most valuable features is that Ansible is agentless. It does not have dependencies, other than Python, which is very generic in terms of dependencies for all systems and for any environment. Being agentless, Ansible is very convenient for everything."
"Ansible provides great reliability when coupled with a versioning system (git). It helps providing predictability to the network by knowing exactly what's being pushed after validating it in production."
"One of the most valuable features is automation. We are doing automation infrastructure, which allows us to automate regular tasks. This solution provides us with a service catalog, like building new services and automating daily tasks."
"It has improved our organization through provisioning and security hardening. When we do get a new VM, we have been able to bring on a provisioned machine in less than a day. This morning alone, I provisioned two machines within an hour. I am talking about hardening, installing antivirus software on it, and creating user accounts because the Playbooks were predesigned. From the time we got the servers to the actual hand-off, it takes less than an hour. We are talking about having the servers actually authenticate Red Hat Satellites and run the yum updates. All of that can be done within an hour."
"Stable solution that's good for automating the CI/CD pipeline: from development to production."
"The most valuable functionality is the ability to define the deployment process, schedule the deployment and automatically execute the deployments to different environments."
"The stability is good. I haven't experienced any issues."
"When you set up Playbooks, I may have one version of the Playbook, but another member of the team may have a different vision, and we will not know which version is correct. We want to have one central repository for managing the different versions of Playbooks, so we can have better collaboration among team members. This is our use case for using Git version control."
"Ansible is great, but there are not many modules. You can do about 80% to 90% of things by using commands, but more modules should be added. We cannot do some of the things in Ansible. In Red Hat, we have the YUM package manager, and there are certain options that we can pass through YUM. To install the Docker Community Edition, I'll write the yum install docker-ce command, but because the Docker Community Edition is not compatible with RHEL 8, I will have to use the nobest option, such as yum install docker-ce --nobest. The nobest option installs the most stable version that can be installed on a particular system. In Ansible, the nobest option is not there. So, it needs some improvements in terms of options. There should be more options, keywords, and modules."
"The area which I feel can be improved is the custom modules. For example, there are something like 106 official modules available in the Ansible library. A year ago, that number was somewhere around 58. While Ansible is improving day by day, this can be improved more. For instance, when you need to configure in the cloud, you need to write up a module for that."
"We would like support for the post-integration of this product before cloud frameworks because right now their approach is to avoid using on-premises activities and move everything to the cloud."
"Some of the modules in Ansible could be a bit more mature. There is still a little room for further development. Some performance aspects could be improved, perhaps in the form of parallelism within Ansible."
"Accessibility. Ansible uses a CLI by default. Those accustomed to it can find their way and adopt the YAML files easily over time. But, some users are more comfortable using UIs..."
"The technical support of the solution could definitely be improved as PMRs take long to resolve."
"I would like to see more reporting for container architecture."
"The scalability of this application needs improvement. Changes and variations in the application become bottlenecks as they need to be more seamless and comfortable."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
Red Hat Ansible Automation Platform is ranked 2nd in Release Automation with 6 reviews while UrbanCode Deploy is ranked 4th in Release Automation with 3 reviews. Red Hat Ansible Automation Platform is rated 8.6, while UrbanCode Deploy is rated 8.6. The top reviewer of Red Hat Ansible Automation Platform writes "Enables us to efficiently manage an almost unlimited number of nodes". On the other hand, the top reviewer of UrbanCode Deploy writes "Stable solution which automates the CI/CD pipeline, but its scalability needs some improvement". Red Hat Ansible Automation Platform is most compared with Microsoft Endpoint Configuration Manager, Red Hat Satellite, VMware vRealize Automation (vRA), Microsoft Azure DevOps and AWS Systems Manager, whereas UrbanCode Deploy is most compared with Microsoft Azure DevOps, GitLab, Nolio Release Automation, Puppet Enterprise and HCL Launch. See our Red Hat Ansible Automation Platform vs. UrbanCode Deploy report.
See our list of best Release Automation vendors.
We monitor all Release Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
