Salt Fundamentals

Salt is an automation framework for running commands, applying desired configuration, and coordinating work across managed systems. A central master can target connected minions, while Salt states describe the configuration those systems should maintain.

itInfrastructure and operations

Don't Panic — Salt Fundamentals

Salt is the part of infrastructure work that lets one place tell many systems what to do, then wait for the receipts. Before that, the usual arrangement was a collection of individual sessions, scripts, and a growing suspicion that one machine had not received the memo.

Salt has two habits worth keeping separate. Remote execution asks selected minions to do something now. States describe the result a system should keep having. The first is an instruction. The second is a promise with a clipboard. Mixing them up is how an urgent command becomes a very elaborate configuration strategy.

The machinery is a master, a service that publishes a job, and minions, services that decide whether its target matches them, run the function, and return data. A target is not decorative punctuation. It decides who hears the job, which makes it part of the blast radius. Start with one explicit minion ID. A wildcard can wait its turn.

Before any of that, a minion presents a key. The master holds it pending until acceptance. Compare the fingerprint first. The slightly surprising part is that Salt's speed does not make this ritual less relevant; it makes a wrong identity or broad target more consequential. Centralized action is still action, only with better postage.

State files, often called SLS files, express outcomes such as a package installed, a file managed, or a service running. Salt checks the current condition and changes it only when needed. A second unchanged apply should report no changes. That quiet second run is useful evidence that the declaration describes a stable outcome instead of repeatedly poking the system to see whether it wakes up annoyed.

The declarations form a graph. Requisites say which state must succeed first, which one reacts to a change, and which one waits for a failure. Grains describe the minion; Pillar supplies master-defined data for selected minions. Those names are peculiar, but their jobs are not: one reports what the system is, and the other provides the configuration it needs.

Start with the Intro for the publish, execute, return loop and the trust boundary. The Slides compress the components and deployment choices into a map. The Cheatsheet holds the command shapes, targeting forms, state operations, and rollout checks. The Practice Reference and exercise turn a managed file into a small, observable proof that desired state can restore drift. After that, the Reference tab is where the precise, current documentation lives, because infrastructure tools are fond of changing details while keeping the nouns.

Don't Panic — Salt Fundamentals

Relevant careers