Salt vs VisualOps: What are the differences?
Salt: Fast, scalable and flexible software for data center automation. Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.; VisualOps: Visual DevOps Automation for Amazon Web Services. VisualOps has a WYSIWYG editor to design, configure and provision your AWS cloud applications. Once the applications are deployed, VisualOps continuously monitors and manages the apps to ensure they always run in the defined states.
Salt and VisualOps can be primarily classified as "Server Configuration and Automation" tools.
Some of the features offered by Salt are:
- Remote execution is the core function of Salt. Running pre-defined or arbitrary commands on remote hosts.
- Salt modules are the core of remote execution. They provide functionality such as installing packages, restarting a service, running a remote command, transferring files, and infinitely more
- Building on the remote execution core is a robust and flexible configuration management framework. Execution happens on the minions allowing effortless, simultaneous configuration of tens of thousands of hosts.
On the other hand, VisualOps provides the following key features:
- drag-n-drop components to build your AWS infrastructure
- clicks instances to setup the software configuration (package, file, code, etc.)
- single click to deploy, within minutes the app is ready to use!
Salt is an open source tool with 10.1K GitHub stars and 4.59K GitHub forks. Here's a link to Salt's open source repository on GitHub.
What is Salt?
What is VisualOps?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Salt?
What are the cons of using VisualOps?
What companies use VisualOps?
Sign up to get full access to all the companiesMake informed product decisions
For automating deployment or system admin tasks, Shell/Perl are more than enough. Specially Perl one liners, that I use heavily, even to make changes in xml files. But quite often the need is to just check the state of system and run scripts without fear. Thats where I actually needed some scripting language with "state mechanism" associated with it. Salt provided me above similar kind of experience. I tested salt first on a small scenario. Installation of 60 RPMS on a machine. I was pleased that I could achieve that in around 25 lines of code using salt. And eventually I was also able to keep data and code separate. This was another plus point. henceforth I was able to use salt to deploy a large potion Datacenter (apps deployment). I am still working towards orchestration and finding it quite promising. The use of pure python whenever needed to deal with more complex scenario is awesome.
When it comes to provisioning tens to hundreds of servers, you need a tool that can handle the load, as well as being extremely customisable. Fortunately, Salt has held that gauntlet for us consistently through any kind of issue you can throw at it.
We've built something using SaltStack and Debian Linux to help us deploy and administer at scale the servers we provide for our part- and fully-managed hosting customers.