Configuration management is a competitive field. Prior to OpenShift 3.0, OpenShift (and largely Red Hat as a whole) had mostly been in Puppet‘s camp with the other major competitor being Chef. When OpenShift started working on its install/configuration for 3.0, it very quickly became clear that Puppet was no longer the obvious choice. So after a large amount of investment in our 2.x Puppet based installer and operational tooling, we decided to start over with Ansible. I won’t claim this route is correct for everyone, but I’ll try to explain our thinking behind the switch.
Quelle: OpenShift
Why OpenShift Picked Ansible
Published by