SaltStack - pain-free infrastructure-as-code
Use Cases and Deployment Scope
We use Salt Open Source Automation Engine primarily to configure our servers. It is used primarily to ensure that all servers are configured in a unitary way and that we have a central repository that defines what is deployed where. We also use it to quickly spin up test infrastructure and to configure developer workstations.
Pros
- Reproducible set up of servers
- Wide array of formulas ("packages")
Cons
- Execution time is sometime longer compared to alternatives
Most Important Features
- Infrastructure as a code
- Separation of concerns using states/pillars/grains
- Flexible deployment - master/minion vs masterless
Return on Investment
- Much faster turnaround in provisoning test environments
- Quicker rollout of services
Alternatives Considered
Open Source Puppet


