Using rosters
Salt was originally designed to operate without the traditional database that many of its forefathers used to store remote system configuration. As its message bus could retrieve information directly from remote machines, often faster than a database lookup, the need for a database was minimized.
As minions connect to the master and not the other way around, in a traditional Salt infrastructure, the master did not even have a need to store the network and host configuration for the minions. The game changes when dealing with SSH-based connections because the master necessarily connects to its minions via SSH.
Rosters were introduced as a means for Salt SSH to keep track of the host information. The default roster, which uses flat text ...
Get Mastering SaltStack - Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.