[chef] Re: Re: Separate Chef servers per environment?


Chronological Thread 
  • From: Nic Grayson < >
  • To: " " < >
  • Subject: [chef] Re: Re: Separate Chef servers per environment?
  • Date: Fri, 24 Jan 2014 09:09:41 -0600

We use different chef servers for staging and production so we can allow staging to be open to all developers. Then production server admin access is only allowed by the ops team. This is mainly due to compliance concerns in our line of work. When something needs to move from staging to production we just knife cookbook upload to the production server. All cookbooks are kept in git repos and tagged when a version is uploaded to staging.

We are in the process of moving to enterprise chef which has much better per environment permissions.

Hope this helps.


On Thu, Jan 23, 2014 at 11:03 PM, Gourav Shah < " target="_blank"> > wrote:



Is anyone running a separate physical Chef server per environment?

ie - staging vs production

If so, how do you handle deployment of changes to roles, data bags, and environments? What process/tooling do you use to move changes into staging first and then into production?


My suggestions here are, 

1.  Use some SCM such as git. 
2.  Push everything to the SCM first, and then pull it from the staging/production servers
3.  Use branching based on the environment names
4.  Version  your cookbooks
4.  Then You could also extensively use Chef environments to use specific versions of your cookbook for wach environment

Thanks
Gourav 
Founder, Initcron
Web:  www.initcron.com
Skype: initcron | Phone: +91 96 2328 2328





Archive powered by MHonArc 2.6.16.

§