3 ms·
I have no strong opinion here, but I am curious to hear yours. What were the discriminators in choosing saltstack over the alternatives? My head spins with th
by DigitalJack 10y ago
I have no strong opinion here, but I am curious to hear yours. What were the discriminators in choosing saltstack over the alternatives?
My head spins with these tools and every time I pick one I seem to eventually run into a road block that is a no-go. The most recent effort was ansible and the no-go was its strict dependency on python2.7.
- dvcrn 10y agoI came from puppet and salt felt a good amount "lighter". I'm mostly a python developer and salt states written in pure yaml with jinja2 templates, or alternatively directly in raw python for more complex stuff feel like home. The yaml makes it very easy to understand even if I come back to a state after months. It's just a list of things that should happen with a few template tags sprinkled in. Not saying salt is better than puppet or friends. It's purely based on preference. I can't say anything to chef or ansible since I never tried them. Salt has a crazy active community and while there are things I don't like about it like the "name" of a state, it's still doing it's job just fine so I sticked with it.
- guitarbill 10y agoha, i moved from chef to ansible for much of the same reasons. at the end of the day, it doesn't matter. (however, from my experience salt and ansible stay readable because they're yaml and not arbitrary code/DSL, whereas chef "recipes" are ruby and usually devolve into complex programs if you're not careful)