mabl is a regression test automation tool with test output visualization and performance regression for tracking the perceived speed of web apps and sites, from the company of the same name in Boston.
N/A
Ansible
Score 9.1 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
We ultimately selected mabl cause it most met our needs and our budget. We needed a low code UI automation test tool. We also have a suite of existing testing tools and other tools that it needed to be able to integrate with. Price was the only thing that ruled out some of the …
Identity Manager focuses on authentication and account management, while Red Hat Ansible Automation Platform focuses on IT automation and system management. Red Hat Ansible Automation Platform was selected because it supports scalable automation, reduces manual administration, …
Our org was using puppet and burning too many people-hours just touching the scripts, troubleshooting, and maintaining why changes were made. Chose Red Hat Ansible Automation Platform as it was much easier to code and follow.
The way its structure it’s just way harder to find and if a script is modified it won’t tell you exactly who made the change or even if a change was made, when it runs it doesn’t tell you what happen and overall it’s really difficult to use compare to Red Hat Ansible Automation …
Managing Puppet can be a full-time job in itself. It requires a client to be installed and managed on each host. If your infrastructure was designed with a certain version of Puppet, upgrading can be very difficult. Ansible is much easier to start using and can deliver value …
We haven't found a scenario yet where it hasn't been appropriate. We did have one function on our application that mabl couldn't do, but they solved it and got back to us very quickly. Our application is web-based and mabl is able to handle this very easily. We use the command line runner a lot. Being able to easily and quickly change from a cloud based run to a local run has been fantastic. Setting up flows and environments is a wonderful feature
I think it's the best defacto orchestrator for automation because it's so easy to integrate in other tools to it (dynatrace, cyberark, terraform, etc). It is a lot for a new or smaller team to use so I wouldn't recommend it to a new team using Ansible, in that case using Ansible navigator is a better start to understanding playbooks/inventories before diving into the complexity of Red Hat Ansible Automation Platform. EDA also takes a lot of connectivity between Red Hat Ansible Automation Platform and target systems to get working which can be difficult in very locked down envs unless you have approval from many other teams like networking and security.
Easy to read sets of instructions to do various things in and out of a pipeline.
Templating
Cloud and on prem provisioning.
Scalability and reusability.
We use it for everything from provisioning hardware for deploying software to it to running pipelines and building containers, etc. It's readable, easy to scale, and great for creating re-usable templates, scripts, or instructions.
I can't think of any right now because I've heard about the Lightspeed and I'm really excited about that. Ansible has been really solid for us. We haven't had any issues. Maybe the upgrade process, but other than that, as coming from a user, it's awesome.
We are extremely happy with the use of AAP. It's better than expected, There is almost no limit when thinking of automation. The only problem is that the day to day is consuming a big part of our time. Patching and checking vulnerabilities are virtually killing us. But we can only improve with AAP.
It's overall pretty easy to use foe all the applications I've mentioned before: configuring hosts, installing packages through tools like apt, applying yaml, making changes across wide groups of hosts, etc. Its not a 10 because of the inconveinience of the yaml setup, and the time to write is not worth it for something applied one time to only a few hosts
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
We ultimately selected mabl cause it most met our needs and our budget. We needed a low code UI automation test tool. We also have a suite of existing testing tools and other tools that it needed to be able to integrate with. Price was the only thing that ruled out some of the above tools, we are a small start up, and don't have a huge budget. Some tools listed didn't have the same functionality or ease of use with the record and playback. mabl works on our machines and integrates with our existing tools
As I said earlier, Red Hat Ansible remains a top choice because it is a perfect combination of multiple capabilities. Terraform is good in IAC but not in config automation. Puppet is well-suited for developers, but not for system administrators and infrastructure integrators. OpenShift and Kubernetes are generic automators only.
A 45min manual process to build VIPs with a SLA of 1 week can now be completed as self-service within 10 minutes in production.
Firewall Policy ranges in review and implementation time depending on complexity of requests. Our policy automation is able to provide detailed and accurate decisioning information that allows the operations team to approve requests and have them automatically implemented within minutes. Not only does this free up Ops for more important efforts, but it opens access many times quicker which allows much faster time to market.
