| We have a mixed Mac and Windows envrionment here, with our Windows side already having a python/yaml based pipeline for Maya and Nuke setup, and I am looking to deploy a CM tool for managing it all. After doing some research it seems that the top choices would be Ansible, Salt, or Chef, and I was hoping to hear from others on their experiences with working with any of them in a mixed envronment, or any reasons to choose one over the others. Here's my basic overview of them: Ansible would be the easiest to deploy and use, since it also uses python/yaml and is agentless. However, it apparently is lacking in the introspection, logging, and documentation department compared to Salt and Chef. Also, couldn't find many people talking about using it with specifically Windows, so I don't know how it performs with Windows or what its limitations might be. Can also be relatively slow in performance.
Salt is more complex than Ansible, but would still be relatively easy to fit in with our existing python/yaml workflow. However, could find even less about using Salt with Windows than Ansible, so also an unknown in regards to that department in terms of actual use.
Chef would be the most complex and difficult to deploy, in particular since it would require us to get used to using Ruby and JSON. It does seem to have the best support for Windows and documentation of all 3 though.
Any thoughts or suggestions are greatly appreci
ated! | |
