Mirantis OpenStack for Kubernetes enables users to deploy, scale, and update bare metal private clouds on Kubernetes substrates.
N/A
Ansible
Score 9.2 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.
$5,000
per year
Pricing
Mirantis OpenStack for Kubernetes
Red Hat Ansible Automation Platform
Editions & Modules
No answers on this topic
Basic Tower
5,000
per year
Enterprise Tower
10,000
per year
Premium Tower
14,000
per year
Offerings
Pricing Offerings
Mirantis OpenStack for Kubernetes
Ansible
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Mirantis OpenStack for Kubernetes
Red Hat Ansible Automation Platform
Considered Both Products
Mirantis OpenStack for Kubernetes
Verified User
Anonymous
Chose Mirantis OpenStack for Kubernetes
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.
Mirantis is a managed service. If you're looking for that type of support, infra management, and to relieve yourself of the burden then they are a great option. If you're looking to build your own cloud and save as much money as possible then running openStack yourself is …
Puppet has Red Hat Ansible Automation Platform beat on metrics. This isn't a fair comparison due to the agent oriented nature of puppet. Ansible is much smoother to start using and appreciably faster to install, configure and role into small groups of systems. I no longer use …
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 is agentless and using SSH so sometimes when the SSH is down we are using since Tanium it is agent base app we using Tanium l to get to the serverand before we were using SALT
I think terraform has some overlap with Red Hat Ansible Automation Platform and what determines which tool would be best will depend on how much can be pushed to the far left vs needing to be flexible or dynamic post deployment
Mirantis OpenStack for Kubernetes is highly scalable and very easy to manage Infrastructure as-a Service (IaaS) platform. It has a built-in Mirantis Kubernetes Engine which is best optimized for bare metal hosts for the best performance. Mirantis OpenStack for Kubernetes is easy to use virtualized Infrastructure as-a Service (IaaS) platform for both cloud-native applications and traditional applications reliability.
I'm going to say it is best suited for configuration management. Like I said, patching even with security, things of that nature. Probably less suited is hardware management, but Red Hat IBM/IBM has Terraform for that. So it's a trade off.
Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks.
Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do.
Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to.
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.
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.
Overall it's good but the new architecture can be complex. Improvements can be made in the Config as Code capabilities for managing Red Hat Ansible Automation Platform. Sometimes it can be difficult for those unfamiliar to understand the relationship between Projects/Credentials/Job Templates, etc.
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.
Mirantis is a managed service. If you're looking for that type of support, infra management, and to relieve yourself of the burden then they are a great option. If you're looking to build your own cloud and save as much money as possible then running openStack yourself is your best option. I would say in the category of OpenStack managed services Mirantis is ahead of Ubuntu (who uses JuJu to manage everything) but behind Rackspace
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.
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.
We are still early in our implementation and don't have much yet - but I can say that it has already improved the time it takes to deploy a new virtual server for us, as well as making them more consistent.
In working through what jobs are required, it has really improved the communication between our different teams
