Mirantis OpenStack for Kubernetes enables users to deploy, scale, and update bare metal private clouds on Kubernetes substrates.
N/A
Salt
Score 6.2 out of 10
N/A
VMware Salt is an Infrastructure Automation & Configuration Management platform that provisions, configures, deploys, and manages infrastructure components at scale. The solution utilizes an event-driven automation engine to enforce compliant software states across virtual machines, servers, containers, and network devices.
The VMware Salt solution is comprised of software components from both VMware and the open-source Salt Project While the Salt Masters and Salt Minions are a part of the open…
N/A
Pricing
Mirantis OpenStack for Kubernetes
VMware Salt
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Mirantis OpenStack for Kubernetes
Salt
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
VMware Salt
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 …
SaltStack is a newer product, so it learned some of the mistakes that Puppet made. It truly is a system that can respond to events as well as configure systems.
SaltStack beats all of the tools above since it is a "6-in-one" solution: Config Management, Orchestration, Automation, parallel sys administration, remote execution and cloud management.
The other solutions only solve one or two problems.
Systems Administrator, Deployment Specialist Consultant
Chose Salt
I've used shell scripts over ssh, custom in-house deployment tools, Chef, and SaltStack. I've evaluated Ansible, but I was never happy with performance over SSH. Chef's loose configuration data model and lack of philosophy and conventions around use makes it difficult for a …
Chef and Puppet both require writing code, which I view as excessively involved for the task at hand. I have only needed to write pure python for a handful of Saltstack use cases - everything else has been configuration files.
Ansible, while elegant and simple, simply does not …
We moved to SaltStack from Puppet about 3 years ago. Puppet just has too much of a learning curve and we inherited it from an old IT regime. We wanted something we could start fresh with. Our team has never looked back. SaltStack is so much easier for us to use and maintain.
I looked at Chef and Ansible but it was a long time ago and I don't remember the pros and cons compared to SaltStack. When I arrived at my company, Saltstack was already used in production so there has been no discussion about other deployment and automation solutions
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.
Managing heterogeneous environments of large numbers of nodes, especially nodes which may need sudden changes (security updates, for instance), or frequent replacement, is a strength for Saltstack. Simplicity is not a strength for Saltstack. In a homogenous environment (all CentOS 7, for example, with no Debian or Windows) I might recommend using Ansible instead - it is less flexible and granular, but simpler to configure.
A superb remote execution framework! SaltStack allows us to easily program numerous functions on top of it. For example, we developed a fast parallel asynchronous deployment tool that handles all software deployment, including interdependent service management.
Configuration management is now easy. We take advantage of this to automate (in tandem with AWS tools) the stand-up of all servers and services. It is also relatively easy to create new configuration management states for software not yet supported by the community (e.g. Grafana).
Flexibility. Numerous small utilities have been built which simply wrap around SaltStack to allow tedious tasks to become easy.
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.
We haven't had to spend a lot of time talking to support, and we've only had one issue, which, when dealing with other vendors is actually not that bad of an experience.
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
I've used shell scripts over ssh, custom in-house deployment tools, Chef, and SaltStack. I've evaluated Ansible, but I was never happy with performance over SSH. Chef's loose configuration data model and lack of philosophy and conventions around use makes it difficult for a team to share responsibility for configuration code. Needing to use additional tools to do orchestration for cross-host/agent dependency relationships made me look for more. SaltStack, while not as mature when I first tried it, impressed me with its speed and elegant design
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.