Mirantis OpenStack for Kubernetes vs. Rackspace OpenStack vs. Red Hat Ansible Automation Platform

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

Need to get an application up and running, then I would say the open stack is a great place to test it out. Why spend time setting things up when you can let them do it for you? Many people also have experience with using Rackspace in some capacity so its an easier learning curve for many people.

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

• 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

• Quick uptime
• Simple Signup
• Lots of options on what you need
• Rackspace is a known company (not some unknown startup)

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

• 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

• Support does not seem to be what it use to be, use to be a solid 10 when dealing with them, now more like an 8
• Pricing can be tricky to figure out
• For some people too many options.

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

Overall, the product is excellent, with daily-use features for both large and small infrastructure. Ansible does its job quickly and ensures compliance, keeping the environment up to date and safe from open vulnerabilities. Large-scale inventory management and license management. Industry standard followed by best practices to maintain continuity. Budget-friendly compared to other products.

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

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

I looked into going with Amazon EC2, was very comparable in pricing, services, options, etc. and a bit cheaper too. Why I did not go with Amazon mainly has to do with knowing Rackspace and being familiar with them. It was easier for me to use a Rackspace product then go with Amazon Elastic Compute Cloud

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

• 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

• Quick setup allowed me to work on the application not setup of where it was going to run
• Expand ability with a few clicks was a great help, no worrying about if I needed more "power", few clicks and I had it.
• Tech support is hit or miss so that can be problematic and that was cause for concern and took time away from development

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