Open Stack

Forrest,

At Workday we are using Chef. The community cookbook are in a very good shape and we are just changing our data bags and environment files.
We have also created a OpenStack Deployment Multi-Node Development Environment based on Vagrant and Docker Containers. It is pretty awesome how easy is to test the chef deployment, actually we are even pushing upstream some enhancements for the cookbooks.

Our company has adopted Chef for all other services and therefore was not really a decision for OpenSatck but actually we are glad with the results. Indeed, at the beginning we had a lot of home-made cookbook that were in conflict with the community ones but our team did a great job fixing and figuring out all those ones.

Cheers,

Edgar

From: Forrest Flagg <fostro.flagg at gmail.com<mailto:fostro.flagg at gmail.com>>
Date: Thursday, March 26, 2015 at 9:40 AM
To: "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150327/739388a6/attachment-0001.html>