An enterprise-grade configuration management system that provides controlled access to software assets.
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
IBM DevOps Code ClearCase
VMware Salt
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM DevOps Code ClearCase
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
IBM DevOps Code ClearCase
VMware Salt
Considered Both Products
IBM DevOps Code ClearCase
Verified User
Anonymous
Chose IBM DevOps Code ClearCase
GIT Stash is superior to IBM Rational ClearCase in many ways. Bundled with SourceTree, the UI is far more modernized and updated than IBM Rational ClearCase. Being able to visually see the individual branches that are created within the repository is much more straightforward …
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 …
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
Rational ClearCase is well suited for a company where development is done from one single location and there are a lot of dependent projects, systems or modules that need to be version controlled. Especially good for a company that creates customized software for clients. Well suited for disciplined development environments. Waterfall methodology mentality seems a better fit for ClearCase than Agile.
ClearCase is not well suited for companies that have development geographically distributed and using Agile Methodologies.
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.
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.
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.
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.
GIT Stash is superior to IBM Rational ClearCase in many ways. Bundled with SourceTree, the UI is far more modernized and updated than IBM Rational ClearCase. Being able to visually see the individual branches that are created within the repository is much more straightforward than the versioning method of ClearCase. GIT also seems to be a lot faster when it comes to checking in/out code and creating the repository.
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