Supermarket 2.3.3 Release


Supermarket 2.3.3 is now available. This release contains bug fixes, minor enhancements, and security updates. Supermarket version 2.3.3 is a recommended update for all users running their own instances of Supermarket. Packages are available in the stable repository. If you are using the Supermarket omnibus cookbook, upgrading to this version can be as simple as a chef-client run on your hosts—if you’ve left the version of Supermarket at the default :latest—or updating your wrapper cookbook’s attributes to ['supermarket_omnibus']['package_version'] = '2.3.3'. The community Supermarket has already been updated.

Security Fixes:

  • Upgraded OpenSSL in omnibus package
Bug Fixes:
  • Fixed display of dependencies for past cookbook versions
  • Added Partner Cookbook badge and search. The upcoming Chef Partner Cookbook program will allow users to find cookbooks jointly developed with Chef by the vendors providing those products.
  • Added chef_versions and ohai_versions to metadata parser in effort towards implementing RFC037
  • Increased the number of contributors shown per page.
Tidying Up:
  • Upgraded RSpec
  • Added rake task to spin up Docker containers for PostgreSQL and Redis in development
  • Added guard for RSpec and Rubocop watchers in development

Posted in release, security, supermarket

Delivery’s Bitbucket (Stash) Integration Released

deliveryandstashOhai Chefs!  We are delighted to announce the release of a new feature in Chef Delivery. Delivery now supports integration with Atlassian Bitbucket v3.x (formerly known as Stash) as a Source Code Provider. With this feature you can create and manage PRs in Bitbucket via Delivery.

Information about setting up the link and the project workflow it enables can be found here. This feature is released as of 0.3.606, which has been promoted to stable and is available for upgrade via delivery-cluster.

In addition to this new integration, if you haven’t upgraded in a while, we have implemented a number of usability enhancements in the dashboard and change pages of the web application.

We hope you enjoy using the Bitbucket integration. As always, we welcome your feedback and invite you to contact us directly or participate in our feedback forum.  Thanks for using Chef Delivery!

Posted in Delivery, release

Chef Server 12.4.1 Release

server-release-wide Ohai Chefs,

We’re pleased to announce that today we’ve released Chef Server 12.4.1. This is a patch to fix upgrades from Chef Server 11 to Chef Server 12.4.

To see the full list of changes, visit the changelog.

The release can be downloaded at

Posted in chef, release

Notes from the Lab: What’s Keeping Marginalized Groups Out of Tech?


An article I wrote with Jez Humble, “The Core Belief Keeping Marginalized Groups Out of Tech,” is available online in Model View Culture [link]. I think it’s an interesting look at some recent trends about what keeps marginalized groups out of tech.

We hear so often about the talent shortage in technical fields — I used to hear it all the time as a university professor. And yet when we look among our ranks, who do we see? A lot of people that look quite similar. More importantly, who do we not see? We don’t see many women, who only make up 15% – 27% of the technical workforce, depending on the data source you cite. We also don’t see people of color, who represent 5% – 7% of technical workers. With one stroke, we could address this talent shortage by reaching out to these underrepresented groups and welcoming them into our world.

My article cites interesting research done by Sarah-Jane Leslie and her colleagues, which was published in Science in January 2015. The research finds evidence that what keeps women and minorities (in this research, African Americans) out of STEM fields is a widespread belief that they are innately incapable of doing the work.

So what can we do? Actively and consistently fight these stereotypes. Work against the belief that, in technical fields,  inborn ability is what matters and that only certain groups have that ability. Foster the belief that what matters is hard work and dedication. Review company processes and correct for any inequalities. Invest in developing your people.

I would encourage you to head over to Model View Culture to check out the article in full. [link]

For those who are interested, here’s the reference for Dr. Leslie’s paper: Leslie, S.J., Cimpian, A., Meyer, M., & Freeland, E. (2015). Expectations of Brilliance Underlie Gender Distributions Across Academic Disciplines. Science, 347(6219), 262-265.

Posted in culture

ICYMI | Chef DOJO: Your DevOps Journey Assessment

On Tuesday, February 2nd, I co-presented a live webinar on the Chef DevOps Journey Assessment or DOJO with Thomas Enochs, VP Customer Success.

The DOJO is an exercise Chef developed to help companies get better results from their DevOps adoption. It gives your team a shared understanding of where you are on your journey and the desired state you’re trying to get to. After we compile the results, patterns emerge and are used to visualize goals and generate custom guidelines towards success.

Watch the recording to find out:

  • Why we created the DOJO and how it can help your organization accelerate DevOps adoption
  • What the DevOps Journey Assessment is and how it’s conducted
  • Who in your organization should attend the DOJO exercise
  • How to get it

Posted in culture, devops, webinar

ChefConf 2016 – Build. Deliver. Delight.

If you’ve been to ChefConf before, you know it’s not your typical tech conference. If you haven’t, this is your year. Our annual get together is like a huge family reunion open to everyone that celebrates a vibrant and passionate community of revolutionaries, game-changers, and disruptors.

ChefConf 2016 takes place July 11-13, in beautiful Austin, TX, bringing together 2,000 IT leaders, practitioners, and innovators from the Chef and wider DevOps communities. We’ll present an invigorating blend of technology and local Austin experiences to engage and energize you no matter your interests, whether League of Legends, BBQ, both, or something in between.


Three lively days will be filled with learning about and sharing the culture and practices that support the DevOps workflow, infrastructure automation, and continuous application delivery. We’ll have inspired discussions, collaborative presentations, and in-depth technical training. In the end, you’ll learn the strategies other organizations have used to successfully put transformation, velocity, and compliance into practice.

The entire event will reach peak-fun the evening of Wed., July 13, with the Chef Community Celebration at a popular SXSW location and Austin classic, the Empire Control Room. This will be the most epic party in ChefConf history and that’s no pose, that’s a promise.

Now, some important details:

  • We want to hear from you! The Call for Proposals is now open. The CFP closes Feb. 29, so tell us your awesome idea today!
  • Visit the ChefConf site to register and save $400 off the standard ticket price before April 15.
  • Get a sense of the schedule and stay tuned for many more details soon.
  • ChefConf takes place at the incredible JW Marriott in Austin. You’ll love it.
  • Still don’t have enough reasons to attend (or get your boss to approve it)? Check out our Justification Letter.
We’re super pumped to be partnering with the artistic and technical communities within Austin to create a conference experience unlike any other. Join us for ChefConf 2016 and join the biggest party in DevOps!

Posted in announcements, chef, chefconf, community, culture, devops, events

Chef Compliance 0.10.4 Release


Chef Compliance 0.10.4 is now available from the Chef downloads site. This is a minor release update which is recommended for all users of Chef Compliance. As you may have noticed, we changed our version scheme. From now on, we bump a minor version whenever we release a new feature, patch version indicate bug fixes.

Here are the enhancements and bug fixes included in this release:


Fixed bugs:
  • Fix date display for scheduled jobs
  • Fix Profile upload path traversal bug
  • Fix tarball traversal
This release also includes InSpec 0.9.11. The full changelog can be found here.

Upgrade instructions for Chef Compliance are found here.


Posted in compliance, release

Using Chef with VMware vRealize Orchestrator


Recently, VMware announced the general availability of their VMware vRealize Orchestrator (vRO) plugin for Chef (formerly vCenter Orchestrator). This plugin offers a number of vRO workflows for interacting with the Chef Server (such as modifying nodes and environments) and bootstrapping new nodes with support for both Linux and Windows nodes.

If you are already using vRealize Automation (vRA) and vRO to provision machines in your environment, the new vRO plugin can be used to help introduce Chef into your environment or help close the gap between existing vRO and Chef use. Here’s an example use case for provisioning new virtual machines:

  • An end user request a new VM using vRA
  • vRA creates the node and executes a “base provisioning” vRO workflow
  • The “base provisioning” workflow performs some enterprise-specific steps for the VM to be usable, such as:
    • Setting the VM’s OS network and DNS configuration
    • Registering it with a DNS service
    • Adding the host to your company’s CMDB
  • The “base provisioning” workflow then executes some vRO Chef workflows, such as:
    • Bootstrapping the node, which installs the Chef software
    • Setting the node’s run list, which would include your company’s “base” cookbook that all nodes must have
    • Setting the node’s environment
    • Executing the first run of chef-client
This combination of vRO and Chef use benefits all users: the VMware team is able to provide a self-service offering to end users for creating VMs and centralizing the provisioning of those VMs, and the end users continue to use the power of Chef to automate the deployment and configuration of your company’s applications.

And don’t forget, the best way to consume vRA and vRO resources as a Chef user is with Chef’s API-driven open-source integration plugins:

  • knife-vrealize: use Chef’s knife tool to create and manage hosts directly using vRA, and execute arbitrary vRO workflows
  • kitchen-vra: use vRA resources from within Test Kitchen to test your cookbooks on vRA-managed  infrastructure
  • kitchen-vro: use vRO workflows to spin up resources to use within Test Kitchen to test your cookbooks
  • chef-provisioning-vra: true “infrastructure as code”, allowing you to provision vRA-managed VMs and other resources from within a Chef recipe
If you currently have a substantial vRO investment within your organization, VMware’s Chef vRO plugin on the Solution Exchange might be a great way to maximize Chef awesomeness for your end users!


Posted in announcements, partners Tagged with: , , , , , ,

Hosted Chef Service Degradation Incident

Hosted Chef Reporting API Increased Error Rates

On January 29th from 07:17 – 15:00 UTC, users may have seen 404 errors being logged at the end of successful chef-client runs as the client attempted to send a run report to Hosted Chef’s reporting service. Additionally, users may have seen empty responses when using knife runs as a client on their workstations. This was a result of 2 of our 16 frontend nodes being left in a incorrect state following a routine deployment. ​

What happened?

​ Chef operations performed a deploy overnight to upgrade chef-server to 12.4* to mitigate several recently released security vulnerabilities. During the course of this deploy, our deploy tooling failed to fully configure the opscode-reporting service on 2 hosts, leaving the hosts in a functional, but degraded state. At this point, the affected nodes were still passing health checks, and were in service behind the load balancer without alerting of any problems. The engineers finished their deployment, and testing the services afterwards saw no indication of the failure because of the limited (~12%) occurrence of the issue. ​

Stabilization steps

​ Once we discovered the problem, in order to quickly restore service engineers manually reconfigured the two incorrectly running nodes which immediately resolved the increased error rates. ​

What we’re doing to improve

​ Chef’s engineering staff is deeply committed to continuously improving our products. We are taking several steps as a result of this incident to improve Hosted Chef. Additional host-level monitoring is being put in place to catch this type of issue more rapidly in the future, also ELB health checks are being updated to more throughly test all components before a node is placed into service behind and load balancer.

The trust and confidence of our users is of the utmost importance to us. We apologize for any inconvenience caused by this incident and will continue to learn from mistakes and improve our systems to give users a better experience.

*A previous version of this article accidentally stated the upgrade was to Chef Server 12.6. The upgrade was actually to 12.4, which is the latest release.

Posted in hosted chef

Chef Analytics 1.2.1 Security Release


We are pleased to announce that Chef Analytics 1.2.1 is now available from This release contains a few minor bug fixes and a security update.

We have updated the version of Ruby on Rails for the Analytics UI to fix a number of posted CVEs.

Bug fixes:

  • Better escaping for strings inside of mustache brackets within rules.
  • Update to the chef-client used within Analytics.
  • New way to gain easy access to the Analytics db with the command opscode-analytics-ctl psql.
  • Default HipChat configuration for notifications was updated to make easier set up out of the box.
Thank you for using Chef!

Posted in analytics, release, security