Release: Chef Client 11.14.2

Ohai Chefs,

Today we have released 11.14.2 of Chef Client. We found a regression while releasing 11.14.0 that was significant enough that we cancelled the release and fixed the bug.


Previous 11.10.0 MVP Nikhil Benesch has once again improved the Chef workflow for all of us, this time for leading the effort on parallelizing cookbook synchronization. Thank you for making this long awaited improvement a reality, Nikhil. We can’t help but name you MVP again! Everyone give @nikhilbenesch a high-five for his continued contributions to the project.


Highlights of the release are:

  • Parallelized cookbook synchronization which dramatically improves the initial Chef run performance.
  • knife serve command which can serve a Chef repository with Chef Zero.
  • Ability to whitelist the saved node attributes during a Chef run.
  • Honoring configured proxy environment variables across the Chef runs.
  • Brand new ffi-yajl gem that fixes several JSON parsing bugs and improves the JSON parsing performance.

You can read more about these highlights here. You can see the full list of changes here.


In this we have more than 40 contributions from the awesome Chef community. Here are the folks who have contributed code to this release:

  • Phil Dibowitz: SIGTERM will once-more kill a non-daemonized chef-client (CHEF-5172)
  • Pierre Ynard: chef-service-manager should run as a non-interactive service (CHEF-5150)
  • Paul Russell: Fix file:// URI support in remote_file on windows (CHEF-4472)
  • John Dyer: Catch HTTPServerException for 404 in remote_file retry (CHEF-5116)
  • Pavel Yudin: Providers are now set correctly on CloudLinux. (CHEF-5182)
  • Joe Richards: Made -E option to work with single lettered environments. (CHEF-3075)
  • Jimmy McCrory: Added a ‘knife node environment set’ command. (CHEF-1910)
  • Hongbin Lu: Made bootstrap report authentication exceptions. (CHEF-5161)
  • Richard Manyanza: Made freebsd_package resource use the brand new “pkgng” package manager when available.(CHEF-4637)
  • Nikhil Benesch: Implemented a threaded download queue for synchronizing cookbooks. (CHEF-4423)
  • Chulki Lee: Raise an error when source is accidently passed to apt_package (CHEF-5113)
  • Cam Cope: Add an open_timeout when opening an http connection (CHEF-5152)
  • Sander van Harmelen: Allow environment variables set on Windows to be used immediately (CHEF-5174)
  • Luke Amdor: Add an option to configure the chef-zero port (CHEF-5228)
  • Ricardo Signes: Added support for the usermod provider on OmniOS
  • Anand Suresh: Only modify password when one has been specified. (CHEF-5327)
  • Stephan Renatus: Add exception when JSON parsing fails. (CHEF-5309)
  • Xabier de Zuazo: OK to exclude space in dependencies in metadata.rb. (CHEF-4298)
  • Łukasz Jagiełło: Allow cookbook names with leading underscores. (CHEF-4562)
  • Michael Bernstein: Add Code Climate badge to README.
  • Phil Sturgeon: Documentation that -E is not respected by knife ssh [search]. (CHEF-4778)
  • Stephan Renatus: Fix resource_spec.rb.
  • Sander van Harmelen: Ensure URI compliant urls. (CHEF-5261)
  • Robby Dyer: Correctly detect when rpm_package does not exist in upgrade action. (CHEF-5273)
  • Sergey Sergeev: Hide sensitive data output on chef-client error (CHEF-5098)
  • Mark Vanderwiel: Add config option :yum-lock-timeout for
  • Peter Fern: Convert APT package resource to use provides :package, add timeout parameter.
  • Xabier de Zuazo: Fix Chef::User#list API error when inflate=true. (CHEF-5328)
  • Raphaël Valyi: Use git resource status checking to reduce shell_out system calls.
  • Eric Krupnik: Added .project to git ignore list.
  • Ryan Cragun: Support override_runlist CLI option in shef/chef-shell. (CHEF-5314)
  • Cam Cope: Fix updating user passwords on Solaris. (CHEF-5247)
  • Ben Somers: Enable storage of roles in subdirectories for chef-solo. (CHEF-4193)
  • Robert Tarrall: Fix Upstart provider with parameters. (CHEF-5265)
  • Klaas Jan Wierenga: Don’t pass on default HTTP port(80) in Host header. (CHEF-5355)
  • MarkGibbons: Allow for undefined solaris services in the service resource. (CHEF-5347)
  • Allan Espinosa: Properly knife bootstrap on ArchLinux. (CHEF-5366)
  • Matt Hoyle: Made windows service resource to handle transitory states. (CHEF-5319, CHEF-4791)
  • Brett cave: Add Dir.pwd as fallback for default user_home if home directory is not set. (CHEF-5365)
  • Caleb Tennis: Add support for automatically using the Systemd service provider when available. (CHEF-3637)
  • Matt Hoyle: Add timeout for Chef::Provider::Service::Windows. (CHEF-1165)
  • Jesse Hu: knife[:attribute] in knife.rb should not override –attribute (CHEF-5158)
  • Vasiliy Tolstov: Added the initial exherbo linux support for Chef providers.

How to get it?

As usual you can get this release with our install script on non-windows platforms:

curl -L | sudo bash -s -- -v 11.14.2

You can download this release for Windows using this link:

Chef Client 11.14.2

Let us know if you run into any issues with this release.

Curry Bot Label Issues – Public Postmortem Meeting

Earlier today we had an issue where Curry Bot added and removed the “Signed CLA” label from a number of pull requests every few seconds causing disruption to workflow and even locking users out of at least one pull request.

At Chef, we conduct postmortem meetings for outages and issues with the site and services. Since Supermarket belongs to the community, and we are developing the application in the open, we would like to invite you, the community, to listen in or participate in public postmortem meetings for these outages.

When: July 31st, 2014 14:00–14:55 PDT (2014–7–31 21:00–21:55 UTC)
Where: Google Hangout link to be provided 5 minutes prior to the meeting via @cwebber and @chef, as well as in #chef on

Getting Ready for Chef + PowerShell DSC

Today we’d like to share the Supermarket debut of the PowerShell DSC cookbook for Chef, an early preview of Chef integration with PowerShell Desired State Configuration (DSC) on Windows. This cookbook allows you to author recipes using any DSC resources available on your system, seamlessly surfacing them as Chef resources you can use in your cookbooks. Integration at this level can greatly expand the universe of manageable configuration points and applications for Windows Chef users.

For detailed requirements on using this prototype cookbook, please visit the README. The prototype is just the start on our journey to delivering fully realized integration of DSC with Chef which we’re working on now.

Read more ›

Guest editorial: “How to find your continuous delivery rhythm” by Jez Humble

The third entry from our upcoming collection of editorials entitled The Quiet Revolutionaries comes from our friend Jez Humble, author of the book Continuous Delivery and principal at ThoughtWorks. Jez examines how the lower cost of product development means companies can now capitalize on subtle market signals, the nature of continuous delivery, and a new kind of minimal viable product. Jez writes:

Read more ›

Webinar: How Scholastic Migrated to AWS with Chef

We’ve got a very cool webinar lined up in a month’s time. On Thur., Aug. 21, at 10 am PT/1 pm ET, our friend Daryn McCool, Manager of eCommerce and Digital Engineering for Scholastic, the world’s largest children’s books publisher, will be detailing the why and how of Scholastic’s move to the cloud.

Daryn’s presentation will be full of best practices guidance and specific, technical details on how to migrate production workloads to the cloud. Primary topic areas include:

  • Why Scholastic needed to move to the cloud

  • Why Scholastic chose AWS and Chef

  • How Scholastic migrated from a legacy IT infrastructure to the public cloud

  • How Scholastic’s cloud infrastructure supports its business

This webinar will include Q&A with Daryn, as well as Chris Munns from AWS and Julian Dunn from Chef.

If you’re considering a move to the cloud, are about to migrate, or are in the midst of planning a migration, this is a must-attend event.

Register here.

Web-Scale IT is here

The way we consume goods and services has fundamentally changed. Thanks to companies like Amazon, Facebook, and Google, we expect delightful, intuitive, always-on digital experiences. And it’s not just consumers. Businesses have the same expectations.

The web innovators changed the physics of IT. Using large-scale compute based on commodity hardware and open source software, Amazon, Facebook, Google, and others created an entirely new approach to infrastructure and applications. An approach that is founded on automation, driven by DevOps, and focused on delighting customers. An approach called web-scale IT.

Research firm Gartner estimates that by 2017, web-scale IT will be found in 50 percent of global enterprises. This shift is already underway – and is the driver of Chef adoption.

Read more ›

Chef Reports Surge in Business and New Platform Features as Enterprises Shift to Web-Scale IT

Company’s Q2 Incremental Recurring Revenue Grows 182 Percent Year-Over-Year with a Quarterly Record Number of New Customers

New Chef Capabilities for Automated Infrastructure Testing, Container Integration, and an Analytics Platform Bring Benefits of Web-Scale IT to the Enterprise

SEATTLE – July 15, 2014 – Chef, the leader in web-scale IT automation, today announced strong business growth for the second quarter of 2014, demonstrating surging demand for its commercial automation platform. Chef also today released new enterprise product features that expand the Chef platform, powering speed, scale, and consistency for enterprise companies who want to accelerate time to market and delight customers through web-scale IT strategies.

Web innovators like Amazon, Facebook, and Google have changed customer expectations about on-demand digital products and services. To meet these expectations, enterprises must adopt practices of the web innovators and make their infrastructures more agile and resilient. Research firm Gartner estimates that “by 2017, Web-scale IT will be an architectural approach found operating in 50 percent of global enterprises, up from less than 10 percent in 2013.”[1]

Read more ›

Release: Chef Development Kit 0.2.0 – Windows support and more

Today we have released a new version for Chef Development Kit a.k.a. Chef DK.

The biggest highlight of this release is the Windows support. Starting with version 0.2.0 Chef DK is now supported on Windows.

Read more ›

Meet the Chef Analytics Platform

The Chef analytics platform is a premium feature of Chef. It provides real-time visibility into what is happening on your Chef server and is the latest in a growing suite of features that will provide a comprehensive view of your infrastructure. Chef analytics runs on separate hardware from the Chef server and consists of several components. Today, we are releasing the first version of the analytics platform, which includes the ability to log Chef actions. Over time, the analytics platform will provide additional capabilities for analyzing metrics and event data from Chef servers and clients.

Read more ›

Release: Chef Container 0.2.0 (beta)

This week, Chef released a version of the Chef client that can run inside a Linux container. This container-friendly client is called chef-container. In this post we’ll give you an introduction to chef-container, its purpose and its components. We’ll also tell you about a new knife plugin for managing container images. Then, we’ll show you how to launch an instance of Apache2, running inside a Docker container.

Read more ›