These events are fired on the Salt Master event bus. This list is not comprehensive.
Fired when a minion performs an authentication check with the master.
Minions fire auth events on fairly regular basis for a number
of reasons. Writing reactors to respond to events through
the auth cycle can lead to infinite reactor event loops
(minion tries to auth, reactor responds by doing something
that generates another auth event, minion sends auth event,
etc.). Consider reacting to
or firing a custom event tag instead.
Fired every time a minion connects to the Salt master.
|变量:||id -- The minion ID.|
Fired when accepting and rejecting minions keys on the Salt master.
If a master is in
will not be fired when the keys are accepted. In addition, pre-seeding
keys (like happens through Salt-Cloud) will not cause
firing of these events.
Fired as a new job is sent out to minions.
Fired each time a minion returns data for a job.
Fired each time a each function in a state run completes execution. Must be
enabled using the
Events fired on a regular interval about currently connected, newly
connected, or recently disconnected minions. Requires the
presence_events setting to be enabled.
|变量:||present -- A list of minions that are currently connected to the Salt master.|
Fired when the Presence system detects new minions connect or disconnect.
Unlike other Master events,
salt-cloud events are not fired on behalf of a
Salt Minion. Instead,
salt-cloud events are fired on behalf of a VM. This
is because the minion-to-be may not yet exist to fire events to or also may have
This behavior is reflected by the
name variable in the event data for
salt-cloud events as compared to the
id variable for Salt
Fired when salt-cloud starts the VM creation process.
Fired when the VM is available and salt-cloud begins deploying Salt to the new VM.
Fired when salt-cloud sends the request to create a new VM.
Fired when salt-cloud queries data for a new instance.
Fired when salt-cloud tags a new instance.
Fired while the salt-cloud deploy process is waiting for ssh to become available on the new instance.
Fired once the deploy script is finished.
|变量:||event -- description of the event.|
Fired once the new instance has been fully created.
Fired when salt-cloud requests the destruction of an instance.
Fired when an instance has been destroyed.