Chef. I've previously used Ansible and Saltstack. I haven't tried any others. When I first started using Chef, it was for work and I wasn't a fan at all. But,

Chef. I've previously used Ansible and Saltstack. I haven't tried any others. When I first started using Chef, it was for work and I wasn't a fan at all. But, it's grown on me to the extent that I replaced all my Ansible-maintained infrastructure with Chef and I now maintain my own personal Chef server. It can definitely be overcomplicated in some scenarios, but I'm comfortable using it and and I feel of the tools I've tried, it allows me to be the most expressive. I'd much rather write a Ruby Chef recipe than a YAML Ansible playbook. The fact that Chef's Management Console UI[0] is available for free (for small deployments) while Ansible Tower[1]'s pricing starts at $5000/yr also factors into my choice. It appears that Red Hat has plans to make a free, open source version of Tower[2] but there's nothing there yet. Looking online, it looks like Saltstack maintains a GUI management console of some sorts, but it's only available for Saltstack Enterprise. [0]: https://docs.chef.io/manage.html https://docs.chef.io/manage.html [1]: https://www.ansible.com/tower https://www.ansible.com/tower [2]: https://www.ansible.com/open-tower https://www.ansible.com/open-tower