Ohai Chefs, We are pleased to announce that Chef Reporting 1.5.6 is now available. This release fixes a few bugs including critical functionality for 2016 partitions in the reporting database. The data is currently collected in 2016 partitions in the 1.5.5 reporting release but without this update it won’t be visible in the UI.

Chef Compliance 0.9.10 is now available from the Chef downloads site. This is a minor release update which is recommended for all users of Chef Compliance. Here are the enhancements and bug fixes added since the 0.9.

Ooyala has been using Chef to configure and provision its deployment framework, Atlantis, for the past year and a half. Now, Ooyala is beginning to incorporate Chef Delivery into its release process. Read about their project in the Skills Library article, Chef Delivery at Ooyala.

A little bit of history… When Chef unveiled Supermarket in 2014 it was intended to be a public community cookbooks site where Chef Community Members could browse cookbooks from anywhere. We were honored that it was received so well! However, we soon discovered a problem.

The votes are in and we have elected our final members for the Chef Board of Governance (CBGB). We will be meeting on a quarterly basis to provide input and formal recommendations regarding the project scope. Please join me in congratulating everyone who has been elected!

Ohai Chefs, ChefSalim here, excited to be bringing you tidings of joy with a release announcement for Chef Client 12.6.0!

What is it? Collaborator Groups are a new way to manage cookbook collaborators in Supermarket. With this feature you can now create groups of collaborators and associate that group with a cookbook or tool.

Chef Compliance 0.9.6 is now available from the Chef downloads site. This is a minor release update which is recommended for all users of Chef Compliance. Enhancements: Remove public key for SSH from UI and API Simplify and improve API documentation found at https://docs.chef.io/api_compliance.

Keeping your Red Hat systems patched is critical, and registering your nodes with Red Hat Subscription Manager (RHSM) or a Red Hat Satellite is the first step. Frequently, users will handle the registration manually or bake it in to their nodes with a one-time startup script.