[chef] Push jobs vs SSH

[Eric Horne < >]

What's the difference between chef push jobs and knife ssh?

I'm researching a use case for chef in which we want highly controlled 
deployments to orchestrate across several different systems. The 
traditional "pull" doesn't fit the bill well because it is difficult to 
get that to coordinate properly across systems.

From what I've read so far, chef push jobs are essentially a daemon 
running on the remote servers that allow arbitrary (but 
pre-defined/whitelisted) execution of commands. Aside from perhaps a 
cleaner white-listing concept (over forced-ssh), how is this different 
(better) than just using knife ssh?

I'm failing to see the benefits or use cases of chef push jobs over 
knife ssh. The documentation is lacking in terms of how it is intended 
to be used. Are push jobs better suited for different situations (and 
what are those situations?)

Thanks for the help!

-Eric