3 ms·
Would be interesting to hear from them on the rationale of why they chose Salt stack compared to puppet, chef or ansible. I figure they must have given it a goo
by volume 12y ago
Would be interesting to hear from them on the rationale of why they chose Salt stack compared to puppet, chef or ansible. I figure they must have given it a good analysis since it seems to be a heavy part of what VisualOps/Madeiera is about.
- tbronchain 12y agoIndeed, this has been a hard decision to make! There are several reasons behind this choice. 1- We think SaltStack is actually taking the right approach of configuration management. Their "states" are easy to understand, and the users don't waste time trying to figure out what does what. 2- We did have thought about Ansible (similar about 1- idea), but their "distribution" approach is different. Indeed, Ansible uses SSH to configure the remote hosts and not a dedicated agent. This is not the was we wanted to take the problem (we are providing or own backend, and using salt only on the agent-side). 3- Even if the technology isn't doing the product, Salt is written in Python. We love Python, and it helped us a lot to integrate their engine in our agent.