mabl vs. Progress Chef vs. Red Hat Ansible Automation Platform

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

Incentivized

Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.

Incentivized

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.

Incentivized

• mabl trainer - record and play back test cases
• Organization - labels and flows make this easy
• Customer support!

Incentivized

• Chef is great at deploying code to both small and large groups of servers.
• We use chef to standup new servers as well as deploy updated code to existing servers and it does this very well.
• Being able to make a change and have it push manually or automatically to any subset of servers has changed the landscape of how our IT teams operate.

Incentivized

• Standardize controls and visibility for automation.
• Provide RBAC and Vault for improved automation security and support.
• Job Scheduling is much more effective than Cron or other home-grown solutions.
• The Red Hat Ansible Automation Platform API is one of the best features as it makes automation accessible from any other platform.

Incentivized

• Asserts could be easier to add, but they aren't terribly hard

Incentivized

• Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
• It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
• Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.

Incentivized

• Ansible is still not truly declarative like Terraform.
• Simple automation is fine, but creating complex, scalable automation scripts is very difficult to learn.
• For a higher number of nodes, Ansible consumes a lot of resources. It needs the paid version of AAP, which requires a cost.

Incentivized

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.

Incentivized

The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation

Incentivized

Everything has room for improvement, but Ansible is the best tool out there for what it does and what it can do. There are plenty of features and capabilities that can be added, but it's just a matter of time before it happens.

Incentivized

It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.

Incentivized

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.

Incentivized

Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.

Incentivized

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.

Incentivized

I spoke on this topic today!

Incentivized

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

Incentivized

We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.

Incentivized

AAP compares favorably with Terraform and Power Automate. I don't have much experience with Terraform, but I find AAP and Ansible easier to use as well as having more capabilities. Power Platform is also an excellent automation tool that is user friendly but I feel that Ansible has more compatibility with a variety of technologies.

Incentivized

The pricing seemed inline with our products in this space. Nothing out of the ordinary in contract, term, or pricing structure

Incentivized

The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience

Incentivized

• We are able to more quickly automate UI tests

Incentivized

• Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
• One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
• Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.

Incentivized

• First, it keeps our entire server infrastructure aligned with our standards and reduces the time and effort needed to maintain our systems.
• Automate routine IT tasks to save time, reduce errors, and ensure every server is configured and updated consistently.
• Tasks that used to take our teams weeks to complete manually now run automatically and reliably, with full visibility, making our infrastructure management more effective and our compliance tracking much easier.

Incentivized