3 ms·

99% of companies I've encountered running SaltStack are masterless anyway.

saltyguy22 7y 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 7y ago
  I'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 7y ago
    not me :D
  - kapilvt 7y ago
    How 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 7y ago
      Ansible 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 7y ago
    Not me
devonkim 7y ago
Salt is a bit of a rarity among ops people but the funny thing is my experience is the opposite of yours - 66%+ of companies I see with Salt run in master/minion mode. I prefer it over Ansible when my ssh settings are super awkward (MFA, multiple bastions, etc) to integrate into an Ansible inventory file. One place with 900+ hosts and 300+ random IP ranges with tons of (badly written) compliance I spent about 3 weeks trying to get an inventory file hacked up and I gave up and deployed Salt within a day for the basic stuff I needed to do for basic running of shell commands from a single point of control.
- busterarm 7y ago
  Most of the places I've seen it are banks. Oddly. Your use case makes absolute perfect sense though -- nice!

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 7y ago
I'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 7y ago
  not me :D
- kapilvt 7y ago
  How 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 7y ago
    Ansible 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 7y ago
  Not me

devonkim 7y ago

Salt is a bit of a rarity among ops people but the funny thing is my experience is the opposite of yours - 66%+ of companies I see with Salt run in master/minion mode. I prefer it over Ansible when my ssh settings are super awkward (MFA, multiple bastions, etc) to integrate into an Ansible inventory file. One place with 900+ hosts and 300+ random IP ranges with tons of (badly written) compliance I spent about 3 weeks trying to get an inventory file hacked up and I gave up and deployed Salt within a day for the basic stuff I needed to do for basic running of shell commands from a single point of control.

busterarm 7y ago
Most of the places I've seen it are banks. Oddly. Your use case makes absolute perfect sense though -- nice!