Ansible Alternatives and Competitors

Get our free report covering Microsoft, HCL, Red Hat, and other competitors of Ansible. Updated: December 2020.
455,108 professionals have used our research since 2012.

Read reviews of Ansible alternatives and competitors

reviewer1414863
System Analyst II at a energy/utilities company with 1,001-5,000 employees
Real User
Sep 9, 2020
A good product for managing patches and updates that could be more robust and up-to-date

What is our primary use case?

Red Hat is an operating system. It has been out since 1995 or 1996 and went through a few iterations before it became a true enterprise solution. Basically, they changed their name and changed the version name back between about 2003 to 2005 when they came to that point. Satellite is a package management solution most commonly used to maintain patch levels and security updates. It is something like what SCCM (System Center Configuration Manager) does on Windows servers and Windows workstations.

Pros and Cons

  • "Satellite gives administrators the ability to target deployments and only send out the updates or provision updates to certain groups."
  • "It cuts down significantly on the administrative time it takes to patch systems in a large environment."
  • "The product could have more diversity in what it is able to deploy and might do better if it was not dedicated to Red Hat products only."
  • "It has not been significantly updated in a while."

What other advice do I have?

On a scale from one to ten where one is the worst and ten is the best, I would rate Red Hat Satellite as about a seven or seven-and-a-half out of ten. It could probably be a bit more robust in some areas. They have not, to my knowledge, done a major revision update in a while. So I would say about a seven or seven-and-a-half is fair. Red Hat has been moving toward an Ansible solution more than the Satellite solution in recent years. That is not really a problem for me. It is just that I would like to see the Satellite server product more updated than it has been. It is a good product for what…
AmitDash
Software Engineer at a tech company with 10,001+ employees
Real User
Feb 20, 2020
Maintains historic versions of artifacts in multiple environments, but the database deployment needs to be more flexible

What is our primary use case?

We use UrbanCode Deploy for storing the artifacts of the environment. In both our production and non-production environments, we rely on UrbanCode as an artifact repository. For example, if we want to deploy something in production then we take our usual steps, such as stopping what needs to be stopped, then we deploy using UrbanCode, and then we restart to make our production environment available again. This solution is also useful for maintaining different versions of the artifacts because it has the capability of maintaining snapshots.

Pros and Cons

  • "The most valuable feature is the snapshot functionality, which allows us to access previous versions of the artifacts."
  • "I would like to have the agent up and running at all times, as opposed to only while it is in the DevOps pipeline."

What other advice do I have?

This is a solution that I recommend but I think that for anybody who is interested in implementing it, I would suggest that they start by reviewing the resources that IBM has online. It is not complicated, and they will be comfortable with how the variables are used and that kind of thing. I would rate this solution a seven out of ten.
Get our free report covering Microsoft, HCL, Red Hat, and other competitors of Ansible. Updated: December 2020.
455,108 professionals have used our research since 2012.