Looks interesting, a quick search on hnsearch shows a post from ~6 months ago that didn't seem to get any attention.
Anyone have any experience with salt in comparison to Chef/Puppet/Fabric setups?
It requires less time invested than fabric for me. Most of the time, the batteries included in salt are enough. When they aren't, it's the same amount of work to maintain as fabric, but salt tends to save me some time building pieces fabric wouldn't provide.
If you maintain multiple linux distros, the templated config files make smoothing over differences in package names or locations a breeze.
If you need to maintain Windows-based stuff, salt can be setup against Windows Server in a manner that wasn't too painful. This was extremely handy when consolidating management of legacy windows stuff with newer linux stuff from the same web gui.
Speaking of web gui, I don't know of any that have significant steam for salt. That said, doing "import salt" in django/flask/$framework and receiving json or pickled data is pretty easy.
The best thing about it for me was the simplicity of storing the configuration -- a bunch of YAML/JSON files that can even be synced over Dropbox/S3 if you want.
Now I just have to convince the others at $work.
(end feeble reply)