using mysql returners

[Stephan Looney]

When using returners,is there a way to avoid having the minions access the database directly to insert the data?

in my environment I only have 4505 and 4506 TCP exposed to the minions. Maybe I am just missing something....seems like the returner would post the data back to the master and insert to the DB from a singular location...

Thanks for the help!

[Stephan Looney]

any one in here know what the expected behavior is on this?

[UnlimitedMoops]

My take on the documentation at http://docs.saltstack.com/en/latest/ref/returners/ is that the mysql returner should work for you.

[David Boucha]

What you want is called the master job cache

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[UnlimitedMoops]

The master_job_cache setting might be helpful. It uses the returner system, but on the master.

http://docs.saltstack.com/en/latest/ref/configuration/master.html

http://docs.saltstack.com/en/latest/topics/jobs/job_cache.html

[UnlimitedMoops]

Good - looks like Mr. Boucha has the same conclusion :). I've seen other implementations, like https://speakerdeck.com/ipmb/monitoring-infrastructure-with-saltstack, but they seem to just plant an external returners db on the master so it wouldn't help you.