Ohai, Chefs! This is my first post on the Chef blog, and I’m thrilled to be part of this fantastic community of innovators. It was great to meet so many of you at ChefConf 2015, where I spoke in the plenary session.
Since I joined Chef, many of you have asked about my role as Director of Organizational Performance and Analytics (OPA!). Broadly speaking, analytics focuses on measurement, metrics, and the analysis of those metrics. My primary mandate is to help Chef continuously improve, whether that improvement be in developing and delivering software, understanding customers, or understanding the DevOps space generally. Like all of you, I want Chef to be an organization that moves at velocity.
As an example of my work, be on the lookout for a series of upcoming posts on this blog about the Chef Community Cookbooks Survey.
For now, I’d like to start by telling you a bit about my perspective on developing a metrics-driven culture, some measures that I think are important to Chef, and a little about what has brought me to Chef.
Read more ›
This year’s Chef Community Summit in London will be held November 3 and 4 and we hope to see you there. Registration is open now, read on for more details.
This marks our second Chef Community Summit in Europe. This year’s Summit will include a single-track of presentations on November 3 and Open Spaces on November 4. Talks will be from our own Chef engineers, leaders, and community members. There will be presentations on topics such as Chef Roadmap, Compliance at Velocity, Chef Provisioning, Analytics, Test Kitchen and Community Participation.
The second day of the Summit is organized as a facilitated Open Space event. This type of event helps ensure that everyone has a chance to participate, the topics discussed are the right topics, and the outcomes are best for everyone.
Community Summits are a terrific place to talk about whatever keeps you up at night regarding Chef or devops. You’ll see a wide variety of topics at the Summit, from deep dives into technical specific problems to “ask me anything” sessions about Chef. What you need to bring is your energy and questions.
Early bird tickets are available for £150.00 each. Registration for this event is limited, so please register today!
8 Eastcheap, Floor 2
London EC3M 1AE
Search for nearby hotel accommodations
Questions? Email us at firstname.lastname@example.org
**Is London a little too far for you to travel? We’ll be hosting our US-based summit in Seattle October 14-15.
We’ve just released Chef Client 12.4.0. This release has a lot of new things:
Better logging options, Windows experience improvements, Resource DSL enhancements,
and much more. You can read about some of the changes below. A full list of changes
can be found in the changelog.
Knife Key Management Commands for Users and Clients in Chef Server 12.1
knife user and
knife client now have a suite of subcommands that live under
key subcommand. These subcommands allow you to list, show, create, delete
and edit keys for a given user or client. They can be used to implement
key rotation with multiple expiring keys for a single actor or just
for basic key management. See
knife user key and
knife client key
for a full list of subcommands and their usage.
You can now have all Chef logs sent to a logging system of your choice.
Syslog can be used by adding the following line to your chef config
log_location Chef::Log::Syslog.new("chef-client", ::Syslog::LOG_DAEMON)
This will write to the
facility with the originator set as
Windows Event Logger
The logger can be used by adding the following line to your chef config file:
This will write to the Application log with the source set as Chef.
Read more ›
It was early April, and I arrived in Santa Clara in the days preceding ChefConf 2015. Levi’s Stadium and the surrounding area was filled with 125,000 wrestling fans. There were seven matches on the main card. The Undertaker contested his first match in almost a year. The Levi’s Stadium attendance record was smashed by six thousand people.
Men, women, families, friends, afros, mullets, tank tops, leather pants, folding chairs, wheelchairs… it seemed as if every possible variant of humanity from all fifty states and forty countries were in Santa Clara, ready to rumble.
In the Hyatt Regency lobby following the main event, it was clear that we have something to learn from WrestleMania about inclusion.
What does it mean to be inclusive? What does it mean when we talk about race, sex, sexual orientation, differences in abilities, and the intersection of all these things?
Read more ›
Matt Wrock is a Principal Software Engineer at CenturyLink Cloud, where he works on data center automation. Many of you are already familiar with Matt from his blog Hurry Up and Wait! Matt writes about many aspects of software engineering, including Chef. He spoke on Entering the Chef Ecosystem From a Windows Background at ChefConf 2015, where he also received the title of Awesome Community Chef. Matt is the project founder of Boxstarter, which automates Windows installations and is a contributor to Chocolatey, a package manager for Windows.
In this blog post, Matt takes us through the Chef-based workflow that he and his team have adopted to automatically update CenturyLink Cloud’s infrastructure in an existing data center.
Creating the local environment
The workflow begins with local development. The following diagram shows the local development environment for creating cookbooks. This environment lives inside of a Vagrant box that is used by anyone at CenturyLink Cloud who works with Chef.
Matt says “We have a repo that’s our application repo. That includes one cookbook, our workstation cookbook, called chef_workstation. That cookbook sets up such things as Chef DK, the links to our Berkshelf API server, links to our Nexus repository manager, the internal gems, Docker and a Rakefile for testing. The cookbook is consumed by a Vagrant file, which first builds an Ubuntu image and then runs the cookbook. When it’s done, you’re in a prompt where knife commands work, you have access to Test Kitchen, and our vSphere provisioning driver.”
Matt noted that, for consistency, the same cookbook that builds the workstations also creates the build agents. If tests pass locally, there’s a good chance that they’ll pass on the test agents. Matt’s team uses TeamCity as its build server.
Read more ›
Please join Chef this week in Boston at the 2015 Red Hat Summit! This is your chance to learn more about Red Hat’s plans for not just Red Hat Enterprise Linux but the many other open source products they work on and provide.
Chef supports Red Hat Enterprise Linux across all of our client, developer and server products. While we currently support Red Hat Enterprise Linux 5, 6, and 7 on x86, we will be adding support for Red Hat Enterprise Linux 7.1 on POWER very soon (contact email@example.com for early access). We also work with their OpenStack offerings and are looking into their newer offerings like OpenShift and ManageIQ.
We recently did a cookbook to kick the tires on Red Hat’s new Project Atomic, a container-based application and services deployment operating system. The cookbook provisions virtual Atomic hosts on top of CentOS 7, deploying the Docker registry, Flannel virtual networking, etcd for service registry, and Kubernetes for cluster management. Stop by the booth and we’d love to show it in action and talk about how the cookbook and Project Atomic work.
We’ll be in booth 1101 and we’re getting started at the Welcome Reception Tuesday night and handing out swag. We’ll be there all week and we’re looking forward to talking about Chef, Red Hat, and anything else you want to discuss.
Today we have releases of Chef Server 12.1.0, Enterprise Chef Server 11.3.2, and Chef Manage 1.17.0 which contain the following security updates:
This update addresses CVE-2015-4335, a remote code execution vulnerability in Redis. We recommend that users of Chef Manage and of Chef Server in HA or Tiered topologies update as soon as possible. Open Source Chef Server 11 is not affected. Supermarket will ship with an updated Redis in the next release. Chef Servers in a standalone configuration are configured such that Redis only listens for local connections; however, we still encourage everyone to upgrade.
Updated packages are available for immediate download on http://downloads.chef.io and via our Apt and RPM repositories.
In addition to this security update, Chef Server 12.1.0 has performance improvements, new features, and bug fixes. Please see the Chef Server 12.1 Release Announcement.
I’m pleased to announce that Chef Server 12.1.0 is now available for download on the Chef Downloads Page and via our Apt and RPM repositories. Here are some of this release’s highlights:
What are the biggest ideas that will shape 21st Century companies?
Opinions vary, but here’s my nomination for the top three:
- Natural Selection. The basic idea is that, over many iterations, the fittest are selected, and the weak wither away. Natural selection has been applied to economics, management theory (read corporate politics), computer programming and other disciplines.
- Conway’s Law. Conway’s Law states that organizations create systems that resemble their communication structures. If the idea of fitness became pervasive in the 20th century, the story of modern corporate change in the 21st is one of breaking down silos, especially between functional contributors to the product development process. DevOps is a famous example. Some extend it to DevSecOps. What’s next? MarkDevSecOps? FinDevMarkSecOps?
- Lean principles. Lean principles were first applied to manufacturing, but the core precepts of Lean thinking have since been applied to many different types of production lines, including software. The main idea is that if you focus on customer value and remove everything that does not contribute to it, you have an efficient, high-value process.
Here’s why I believe these three ideas are so important. External regulatory frameworks are not themselves responsible for the existence of competition, but they set the boundaries of the game. In other words, they alter the environment
in which naturally occuring economic selection takes place. The beak of the finch
has to meet EU standards!
Read more ›
We’re pleased to announce that Chef Server 12.1.0 RC3 is now available for download. RC3 is the follow-up to RC1, which we announced on May 28th.
What’s New Since RC1
- Erlang 17: We’ve upgraded the Erlang distribution that we ship with the Chef Server to Erlang 17.5
- Solr Upgrade Fixes: We’ve fixed an issue that prevented Chef Server from running the latest version of Solr after an upgrade. If you upgraded from a previous version, you would continue to run the version of Solr that shipped with that Chef Server.
- Actions Messages Password Filtering: The Chef Server now filters out password information before sending data off to the Chef Analytics queue.
What happened to RC2
We had to skip RC2 for this release because it encountered a failure during the build and release process. Remediations were made to the process and the version was bumped to RC3 accordingly. RC3 is the follow-up release to RC1.
Where Can I Download It
Release Candidate builds of the Chef Server can be downloaded from the Packagecloud current repository. The direct links to the build are: