gtmanfred
commented
6 years ago No events get published to the publish bus.
The minion bus and the master bus are just event busses, for state.event or any fire_event stuff. They are used by the reactor, as well as interprocess communication, so that we can do stuff like refresh grains asyncronously.
The publish bus is where the master puts the jobs, it publishes jobs and this is where minions pick up jobs to run.
The syndic is just a means of copying from bus to bus. So the it redistributes published jobs to the publish bus of the master that it lives on. and then any return events that get sent to that master, or any events at all sent to that master, get republished to the event bus of the master of masters.
If you have masters in failover, the only event bus used it the one on the active master, but if you have active-active masters, it gets sent to both masters, or is allowed to pull jobs from both masters.
I am going to mark this as a documentation issue.
stale[bot]
AstraLuma
sagetherage
As a Salt user getting into deeper module writing, I've found the various message busses to be very confusing.
When an event is published, it can go (as far as I know):
state.eventrunner, and other places?)I have little idea about how these busses interact, or how they interact with more complex configurations (syndics? Round-robin masters?)
It was also entirely unclear when I got started on these deeper topics that these various busses even existed.