In Chef’s Customer Engineering team we are frequently asked for advice on tuning the Chef Server for high-scale situations. Below is a summary of what we generally tell customers. Note that these tuning settings are specific to Chef Server 12, which is the recommended version for any customer who cares about the performance of their Chef server.

This is an updated version of the previous post from August, 2014: Getting started with oc-id and Supermarket

Chef Server 12 includes oc-id, the OAuth2 service that powers id.chef.io. After upgrading to this release, Chef customers can now run their own Supermarket service behind a firewall.

Description

Source code at: https://github.com/irvingpop/rhcs7

I created a Vagrant-based configuration that brings up two CentOS 7 nodes that share a cluster disk with CLVM. Based on: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/High_Availability_Add-On_Administration/ch-startup-HAAA.html with clarification from: http://www.davidvossel.com/wiki/index.php?title=HA_LVM

Ultimate goal: Find a way to couple Redhat clustering with Chef Server to create a more robust HA stack.

Hello, World!

Daisy, Daisy, etc etc.

def foo
  puts 'wat'
end