Incorporating external data sources
We've taken care of Salt keys, but we have some other directories that we need to distribute among the masters. Let's start with a component that is used every time you issue a command from the master to one or more minions: the job cache.
The external job cache
Before we dive into this component, let's review the master job cache:
When a command is issued, a job ID (JID) is created on the master.
Information about that job is stored in the job cache, such as what the command and its arguments are and which minions will be affected.
The job data is posted to the message queue, where the affected minions pick it up and perform the requested work.
When each minion finishes the task, it sends the return data back to the master, where it is also stored in the job cache.
If the
saltcommand is still running, it will pick up the job data and display it to the user.
In this workflow, the minion will always return data to the master, whether or not the salt command is...