ranjib

Grab the validation client in json format from old chef server

knife client show chef-validator -c knife-chef-server-10.rb -Fj > chef-validator.json

Upload the validation client to new chef server, delete the existing validation client from new chef server first, as update(PUT) is not allowed, only create(POST) is allowed

knife client delete chef-validator -y -c knife-chef-server-11.rb

ranjib

require 'chef'
Chef::Config.from_file('knife.rb')
envs = Chef::Environment.list.keys
q = Chef::Search::Query.new
envs.each do |e|
  constrained_cookbooks = Chef::Environment.load(e).cookbook_versions.keys
  all_cookbooks =[]
  nodes = q.search(:node, "chef_environment:#{e}").first.reject(&:nil?)
  nodes.select{|n| n.attribute?(:recipes)}.each do |n|
    n.recipes.map{|r| r.split('::')[0]}.each do |cookbook|

aphyr

Writes completed in 26.395 seconds

800 total
765 acknowledged
770 survivors
5 unacknowledged writes found! ヽ(´ー｀)ノ
(30 31 32 33 34)
0.95625 ack rate
0.0 loss rate
0.006535948 unacknowledged but successful rate

fnichol

SUITE_NAME=default

# create a bats subdirectory under your desired suite
mkdir -p test/integration/$SUITE_NAME/bats

# create an initial "canary" bats test file
# more examples at:
# * https://github.com/fnichol/chef-rvm/tree/master/test/integration/rubies/bats
# * https://github.com/fnichol/chef-ruby_build/tree/master/test/integration/alltherubies/bats
# * https://github.com/sstephenson/bats

logikal

John Allspaw

Dr. Neil J. Gunther - http://perfdynamics.blogspot.com/2013/03/monitorama-2013-conference.html

Mathias Meyer

Cliff Moon

John E. Vincent

aphyr

Some people think that configuration should not be "Turing complete"; others think the configuration language should be as expressive as possible--so much so that it amounts to a programming language itself.

I assert that configuration files which are not Turing complete (or, perhaps a more useful distinction, are not "sufficiently complex languages") are in practice extended to be that complex; and when that happens, the result is often more difficult to understand than if the language were more powerful to start with.

fujin

(setq ruby-deep-indent-paren nil)
(defadvice ruby-indent-line (after unindent-closing-paren activate)
  (let ((column (current-column))
        indent offset)
    (save-excursion
      (back-to-indentation)
      (let ((state (syntax-ppss)))
        (setq offset (- column (current-column)))
        (when (and (eq (char-after) ?\))
                   (not (zerop (car state))))

kixorz

{
  "Statement": [
    {
      "Action": [
        "route53:ChangeResourceRecordSets",
        "route53:GetHostedZone",
        "route53:ListResourceRecordSets"
      ],
      "Effect": "Allow",
      "Resource": [

jimweirich

# My take on Mike's source_for method.
# (see http://pragmaticstudio.com/blog/2013/2/13/view-source-ruby-methods)
#
# (1) I named it 'src' rather than source_for (ok, I'm a lazy typer).
# (2) The edit function was broken out as a separate function.
# (3) The edit function is for emacs
# (4) If the method is not defined on the object, and the object 
#     is a class, then see if it is an instance method on the class.
#
# The fourth point allows my to say:

roidrage

require 'connection_pool'
require 'redis'
require 'metriks'

class RedisClientWrapper
  def initialize(options)
    @options = options.delete(:pool)
    @pool = ConnectionPool.new(@options) do
      ::Redis.new(options)
    end