What do you like most about Red Hat Ansible Automation Platform?

The most valuable features of the solution are automation and patching.

We can automate a few host configurations using the product.

The playbooks and the code the solution uses are quite useful.

The most valuable features of the solution are its configuration management, drift management, workflow templates with the visual UI, and graphical workflow representation.

The most valuable feature is that Ansible is agentless.

Feature-wise, the solution is a good open-source software offering broad support. Also, it's reliable.

Red Hat Ansible Automation Platform is quite stable. If you set it up correctly with the right configurations and there are no hiccups during installation and deployment, it will be stable.

I'd give stability a rating of eight out of ten.

The most valuable features of Red Hat Ansible Automation Platform are the agentless platform and writing the code is simple using the Yaml computer language.

The solution is capable of integrating with many applications and devices in comparison to BigFix.

I like the fact that Ansible is agentless.

The automation manager is very good.

The solution is very simple to use.

Some colleagues and other companies use it and comment that it is easy to use, easy to understand, and offers good features.

I like the agentless feature. This means we don't install any agent in worker nodes.

There are new modules available, which help to simplify the workflow. That is what we like about it.

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.

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.

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.

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.

It is very easy to use, and there is less room for error.

The biggest thing I liked about Ansible is the check mode so that we can verify, after we've pushed, that the config there is actually what we intended.

The Organizations feature, where I can give clear silos and hand them over to different teams, that's amazing; everybody says that it's their own Tower. It's like they have their own Tower out there.

It enabled me to take the old build manifest and automated everything. So when it came time to spin everything up, it was quick and simple. I could spin it up and test it out. And then, when it came time to roll production, it was a done deal. When we expanded to multiple data centers, it was same thing: Change a few IP addresses, change some names, and off we went.

Having the Dashboard from an admin point of view, and seeing how all the projects and all the jobs lay out, is helpful.

Managing our inventory is a big pain point. Right now, we have Satellite, but we can tie it in with Satellite, so we can actually manage things and automate the entire deployment stack, instead of trying to grab things from tickets, then generating Kickstart, and using that to get things in Satellite. That doesn't work well. We can do the whole deployment stack using the inventory share between Tower and Satellite.

On the network side, I already have a lot of our firewall related processes automated. If it's not automated all the way from the ticket system, our network team members, our tier-one guys in India, can just go into the Tower web interface and fill in a couple of survey questions.

Its checking and validating ensures our packages are properly patched.

I like being able to control multiple systems and push out updates quickly with just a couple of clicks of a button and commands. I like the automation because it is a time saver.

It was easy to read and learn. It is a YAML-based syntax, which makes it easily understand and pick up.

It is agentless. I don't have to think about which client system my unit has understanding in or not, because I can execute from my system. It will go and configure it, and any module that it is looking for will be shipped out.

Since it is in YAML, if I have to explain it to somebody else, they can easily understand it.

Installing it is a PIP command. So, it's pretty easy. It is a one liner.

It has made our infrastructure more testable. We are able to build our infrastructure in CI, then are more confident in what we are deploying will work, not breaking everything.

It is very extensible. There are many plugins and modules out there that everybody helps create to interact with different cloud providers as well.

It is quick to production. It has an API in the back which allows for integrations.

The user interface is well-built and very easy to navigate around.

The most useful features are the playbooks. We can develop our playbooks and simplify them doing something like a cross platform.

This solution allows us to stitch a lot of different parts of the workflow together.

The automation is the most valuable feature.

Ansible Galaxy is helpful for roles and Git Submodules: No dependency in managing playbooks. Also, fact caching in redis for host/role grp information speeds up execution. Finally, variable management is easy.