Overview
What is Salt?
Built on Python, Salt is an event-driven automation tool and framework to deploy, configure, and manage complex IT systems. Salt is used to automate common infrastructure administration tasks and ensure that all the components of infrastructure are operating in a…
SaltStack - pain-free infrastructure-as-code
SaltStack doesn't make me feel Salty.
Spicing up Linux infrastructure management
SaltStack is able to provide …
Seasoned advice about SaltStack
SaltStack is recommended!
Saltstack is complicated and beautiful - a rare combination
SaltStack is AMAZING!!
Why would you pick Salt over Ansible
Saltstack give your operation tasks a sweet taste
Saltst…
Better start using SaltStack today - and save lots of your time tomorrow!
Pricing
What is Salt?
Built on Python, Salt is an event-driven automation tool and framework to deploy, configure, and manage complex IT systems. Salt is used to automate common infrastructure administration tasks and ensure that all the components of infrastructure are operating in a consistent desired state.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
17 people also want pricing
Alternatives Pricing
What is Ansible?
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…
Product Demos
SaltStack agentless management using salt-ssh
SaltStack salt-ssh quickstart
Product Details
- About
- Tech Details
What is Salt?
Salt is presented as ideal for configuration management because it is pluggable, customizable, and plays well with many existing technologies. Salt enables users to deploy and manage applications that use any tech stack running on nearly any operating system, including different types of network devices such as switches and routers from a variety of vendors.
Salt Technical Details
Deployment Types | On-premise |
---|---|
Operating Systems | Windows, Linux, Mac, FreeBSD |
Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(35)Community Insights
- Business Problems Solved
SaltStack has proven to be an invaluable tool for managing complex IT infrastructures and automating critical infrastructure tasks. Users have reported using SaltStack to manage configurations on over 100 CentOS virtual machines, simplifying the setup process and efficiently configuring essential elements such as NTP, DNS, user accounts, and automounted NFS home drives. The ability to install base package sets for different machine types based on their respective groups has further streamlined the configuration process.
Additionally, SaltStack is being utilized in various environments, including integration lab environments for instructional workshops and cloud-based development projects. Its orchestration capabilities allow users to easily configure highly available architectures and automate server management tasks. Furthermore, SaltStack's extensive feature set in configuration management, orchestration, remote execution, and cloud management make it a preferred choice for managing large fleets of systems at scale.
Organizations across industries have found SaltStack to be an essential tool for their needs. Some companies have built custom deployment orchestrators on top of SaltStack to automate critical infrastructure across multiple VPCs in AWS, while others rely on it organization-wide for configuration management, continuous delivery, user management, package management, and data distribution. Overall, SaltStack's versatility and robust functionality make it an indispensable asset in managing complex IT environments efficiently and effectively.
Attribute Ratings
Reviews
(1-10 of 10)SaltStack - pain-free infrastructure-as-code
- Reproducible set up of servers
- Wide array of formulas ("packages")
- Execution time is sometime longer compared to alternatives
SaltStack doesn't make me feel Salty.
- Event engine/configuration.
- Vulnerability reporting.
- Compliance.
- It's growing fast, so stability.
Spicing up Linux infrastructure management
SaltStack is able to provide many benefits within one set of tools: Configuration Management, Orchestration, massive parallel sys administration and remote execution and cloud management.
With SaltStack, one is able to manage complex IT infrastructures, consisting of internal and external provides (such as Azure, for example).
- Configuration Management
- Parallel system administration
- Remote Execution
- Cloud connectors
- Orchestration
- Update and patch management
- Automation
- Managing network hardware should be more native and easy
- SaltStack should buffer jobs and, when a client returns, make sure it is executed proberly
- SaltStack should provide basic pillar and states structures to help get newbies started
Seasoned advice about SaltStack
- One tool to provide both configuration management and orchestration at any scale.
- Modular and extensible code (modules, formulas, packages) with a very active community promotes community-style development within your own organization.
- Great documentation has made massive strides in the past two years.
- Masterless (serverless) and salt-ssh (agentless) features are not as well documented or easy to use as other competitive technologies (ie. Ansible).
- Debugging YAML+Jinja templated configuration is getting better, but is still occasionally frustrating. Diligent testing on small changes helps, but it's easy to get lost doing too much too fast.
- Best practices and features have improved a lot in the past year, but much of the community code needs to be updated to take advantage of them.
SaltStack is recommended!
- 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.
- There are no big issues with SaltStack. I'll highlight a few minor items to consider here. One is version numbers of the software. This can be a little confusing to newcomers.
- The documentation is good now, but used to be lacking.
Configuration Management
Orchestration of Services/Applications in regard to each other or infrastructure
Custom tooling - wonderful event bus for asynchronous event driven actions
Instant remote access (command execution) to tens/hundreds/thousands of servers with very flexible targeting
Ability to put network nodes under configuration management even if they are unable to run a "minion" via proxy minions
Less appropriate use of SaltStack? If you have only one server and want to manage it very poorly resulting in difficult hours of trouble-shooting then don't use SaltStack.
Saltstack is complicated and beautiful - a rare combination
- Targeting is easy and yet extremely granular - I can target machines by name, role, operating system, init system, distro, regex, or any combination of the above.
- Abstraction of OS, package manager and package details is far advanced beyond any other CRM I have seen. The ability to set one configuration for a package across multiple distros, and have it apply correctly no matter the distrospecific naming convention or package installation procedure, is amazing.
- Abstraction of environments is similarly valuable - I can set a firewall rule to allow ssh from "management", and have that be defined as a specific IP range per dev, test, and prod.
- Saltstack could use more intermediate-level documentation and tutorials. Most of the information out there tends to leap from "install apache" (the "hello world" of configuration management) straight to the most complex scenarios.
- Similarly, more outreach to a wider audience would be useful. In the same way that widespread use of git and vim makes these easy stacks to require of new engineers, widespread use of Saltstack by amateurs and dabblers would be helpful 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.
SaltStack is AMAZING!!
- Very easy to run a single command against multiple machines at once
- Low maintenance once after the initial configuration is done
- Very easy to install and configure clients (minions)
- There is a little bit of a learning curve to figure out the syntax to the configuration
Why would you pick Salt over Ansible
- Rich, powerful DSL
- Highly scalable – fast, parallel deployment to dozens of nodes
- Strong community
- Steep learning curve
- No sandbox, dry run, or execution plan mode. It's hard to iterate quickly during development, and quite easy to break things during development.
- Copying huge amount of small files is slow and suboptimal — make sure to package your software into tarball/dpkg/your favorite package format if you need to copy it to the instance.
In practice, this means with Salt it's trivial to build an AMI which will pull state from master on startup and bring the new instance into service. You can use that instance with AutoScaling group, and voila — you have a scalable cluster on full auto.
Saltstack give your operation tasks a sweet taste
Saltstack is used for deployment on the different nodes in a consistent way.
- Easy to configure and maintain since it is centralized, and there is also discovery
- Can adapt to a lot of situations with the minimum of configuration. It is easy to write and deploy our own templates and modules
- The documentation is easy to read and exhaustive
- Having a centralized master lead to a single point of failure. Having a native distributed architecture would be appreciated
- Dynamically generated configuration files with Jinja.
- Software deployment and configuration automation.
- Very simple YAMLl/Jinja syntax.
- It's easy to install and maintain.
- Still lots of bugs, but they are being fixed pretty quickly.
- We sometimes have scaling problems while running hundreds of states across hundreds of servers.
- Out of box reporting is not clear. For example, I launched installation of the new package across 400 servers, and I only want to know where it FAILED - it's not easy with SaltStack.