As mentioned before I think organizations tend to go with what they already have. It is a huge project to switch from x to y if you have a significant amount of investment/code in x. Having 2 different configuration management systems within one organization is no fun either.
I have quite a bit of Puppet knowledge and it sorta works. One thing I dislike about Puppet is that some stuff that is conceptually trivial to do requires jumping to burning hoops, if possible at all, in Puppet. Most of those things would have been 2 seconds work if I could just use python. Which brings me to my next point: If you have a blank slate and no investment in any technology I would recommend looking at Saltstack. One of the many benefits is that it is Python based. I liked this comparison between Saltstack and Ansible: http://ryandlane.com/blog/2014/08/04/moving-away-from-puppet-saltstack-or-ansible/ Note that I have no experience with Saltstack so it might just be that the grass looks greener on the other side of the fence ;) Cheers, Robert van Leeuwen From: Forrest Flagg <fostro.fl...@gmail.com<mailto:fostro.fl...@gmail.com>> Date: Thursday, March 26, 2015 at 5:40 PM To: "openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>" <openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>> Subject: [Openstack-operators] What are people using for configuration management? Puppet? Chef? Other? Hi all, Getting ready to install a Juno or Kilo cloud and was wondering what people are using for configuration management to deploy openstack. Are you using Puppet, Chef, something else? What was the decision process for making your choice? Thanks, Forrest
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
