IBM DevOps Code ClearCase vs. Mirantis OpenStack for Kubernetes vs. Red Hat Ansible Automation Platform

IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control

Incentivized

Mirantis is well suited for someone who doesn't mind spending money but doesn't quite want to commit to a cloud provider like AWS. It is also well suited for small or junior technical teams that don't have the skills, experience, or time to run their own openstack clusters.

Incentivized

Red Hat Ansible automates server management, configuration updates, and deployments across our server infrastructure, keeping everything consistent, reducing human error, and saving time. Also provides detailed reports on what is done and uses role-based access controls to keep systems secure by controlling who can make changes.

Incentivized

• Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
• Rational ClearCase handles parallel development of many dependent applications really well.
• The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.

Incentivized

• Can be deployed and run on bare metal on premises clouds
• Is highly reliable and highly scalable
• One of the good performance private cloud IAAS platforms available around

Incentivized

• It reduces custom scripting efforts because everything can be scripted in simple, human-readable YAML playbooks.
• Not only servers, but also network devices, VMs, Containers, Kubernetes clusters, etc., can be automated via Ansible, showcasing its extensive list of supported devices.
• It is agentless, which makes it lightweight and allows for easy integration into CI/CD and GitOps pipelines.
• Many Tier-1 telcos use Ansible for Day 0/1/2 automation of RAN, transport, and core infrastructure (e.g., network function lifecycle management, NE configuration push, patching VNFs).

Incentivized

• Extremely buggy.
• Sometimes the repository gets locked for no reason.
• Slow.

Incentivized

• Mirantis OpenStack managed services are expensive. Very expensive for a start-up.
• I'd personally like to see a little more under the hood details in the status pages.
• Mirantis could also benefit heavily from a free "light" version that start-ups could use to run their own cloud. Maybe coupled with advertising or some sort of surveys.

Incentivized

• 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.
• Give out Lightspeed for free.

Incentivized

Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.

Incentivized

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

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

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

If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.

Incentivized

Mirantis OpenStack for Kubernetes is easily manageable and has seamlessly configurable containers. It also has high reliability and security, which is certainly a positive point for this product. Overall I think it is a worthy competitor in the market to compare for your needs.

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

• Managed code versioning for many years.
• Only one person can edit code at a time - slows processing down.
• IBM is an expensive product to support.

Incentivized

• Mirantis did help our business figure out if openstack was right for us.
• Using Mirantis I felt a bit cheated on understanding the deep technical knowledge of how openstack works. But that being said that is probably a value add more than a detractor for most people.
• Using Mirantis was considerably cheaper than AWS.

Incentivized

• POSITIVE: currently used by the IT department and some others, but we want others to use it.
• NEGATIVE: We need less technical output for the non-technical. It should be controllable or a setting within playbooks. We also need more graphical responses (non-technical).
• POSITIVE: Always being updated and expanded (CaC, EDA, Policy as Code, execution environments, AI, etc..)

Incentivized