3 ms·
Depends on their use case. IMO, Salts best feature is probably running with the Master / Minion setup because it connects out to the master. Masterless is hand
by saltyguy22 6y ago
Depends on their use case.
IMO, Salts best feature is probably running with the Master / Minion setup because it connects out to the master.
Masterless is handy for using in conjunction with Vagrant, Packer, or another provisioning tool not so much for managing a the lifecycle of a server / OS.
- busterarm 6y agoI'm not clueless. I know this. This doesn't detract at all from what I said. In production, an outsized number of companies are using SaltStack a certain way. The reason is because of the way we all evaluate business risk. I could have said that out of all of the companies I've worked with using Salt that have compliance requirements, 100% of them are using it Masterless, but then some smart-ass would have piped up with a "not me" comment.
- Ascetik 6y agonot me :D
- kapilvt 6y agoHow would you compare it to ansible in that usage model? I don't do much config mgmt these days, so curious for a master(less) mindset, whats the comparison for salt vs. ansible?
- busterarm 6y agoAnsible gets a ton more use. Its push model is highly favored in IT organizations. Salt's event/reactor system has tricks Ansible can't do.
- rexarex 6y agoNot me