Inside the new AWS OpsWorks for Chef Automate service

We’re excited about this morning’s announcement at AWS re:Invent unveiling the new AWS OpsWorks for Chef Automate service. This service helps anyone get started quickly with Chef Automate in a low-risk low-friction way with all the benefits you’d expect from any native AWS service. This launch is the result of a tight partnership between Chef […]

Read More

Erchef Comes to Hosted Chef

I’m very happy and quite proud to announce the successful deployment of erchef on Hosted Chef this week. Getting erchef into Hosted Chef has been a long and challenging project involving a good chunk of Opscode’s engineers. Since the successful cut over to erchef, our Hosted Chef customers have seen marked reductions in API timeouts […]

Read More

Turn it to 11: Upgrading From Chef 10

Editor’s Note: A previous version of this blog post recommended setting cookbook\_path to nil in the knife.rb file. That line has been removed, as it causes an error in newer version of knife/chef-client. Either do not set the cookbook\_path or do not set it to nil when following these instructions.  You can find instructions on […]

Read More

The Making of Erchef, the Chef 11 Server

The Chef 11 Server provides significant improvements in terms of compute efficiency, scalability, and operability. We achieved these improvements by rewriting the API server in Erlang and switching the data store from CouchDB to PostgreSQL. This post provides a behind the scenes look at some of the engineering decisions and development approaches involved in creating […]

Read More

Chef 11 Released!

We’re incredibly proud to share the latest major release of Chef with you. The Chef Client and Chef Server are now separate projects. We will be making separate but compatible releases moving forward. You can download both of them from the Chef download page. Erchef, the Chef 11 Server The most significant new feature is […]

Read More