Anthony Scalisi scalp42

Notifications from Resources "Bubble Up"

Release in Chef 12.9.41 via PR #4741 core chef now has a feature which has been available in Poise for awhile, which is that notifications from within resources will now notify resources in outer run contexts. This means you can write a recipe with a service resource and send a notification to it from a resource that you write.

Notifications will bubble up from arbitrarily nested resources, so users that write resources that wrap resources which wrap your resource will still find the service resource in your default recipe.

At the same time the resources collection #find() and #lookup methods and the more commonly-used DSL method resources("service[ntpd]") has been changed to also match

About the pic

Choria supports Federating multiple collectives of nodes into a large Federated collective for the purpose of orchestrating.

Federation Requests have:

A orchestration request as normal
Special headers listing which nodes its for

The client chops a large request into bundles of 200 nodes and publish them to the network for federation. Multiple federation brokers can thus take care of distributing it.

	<!DOCTYPE html>
	<html>
	<head>
	<title>Maintenance</title>
	<style>
	body {
	background: black;
	padding: 25px;
	}
	div {

	#!/usr/bin/env ruby

	require 'net/http/persistent'
	require 'uri'
	require 'thread'

	USAGE = <<EOS
	Parse a Rails log file and send metrics to stathat

	export EMAIL=email

	$> TF_LOG=debug terraform apply terraform

	2019/03/21 11:35:01 [INFO] Terraform version: 0.11.13
	2019/03/21 11:35:01 [INFO] Go runtime version: go1.12
	2019/03/21 11:35:01 [INFO] CLI args: []string{"/usr/local/Cellar/terraform/0.11.13/bin/terraform", "apply", "terraform"}
	2019/03/21 11:35:01 [DEBUG] Attempting to open CLI config file: /Users/scalp/.terraformrc
	2019/03/21 11:35:01 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
	2019/03/21 11:35:01 [INFO] CLI command args: []string{"apply", "terraform"}
	2019/03/21 11:35:01 [INFO] command: initializing local backend from plan (not set)
	2019/03/21 11:35:01 [DEBUG] checking for provider in "."

	$> terraform plan -out terraform

	provider.aws.region
	The region where AWS operations will take place. Examples
	are us-east-1, us-west-2, etc.

	Default: us-east-1
	Enter a value: us-west-2

	Refreshing Terraform state in-memory prior to plan...

	I, [2018-03-26T12:32:33.166713 #89666] INFO -- Kitchen: -----> Starting Kitchen (v1.20.0)
	I, [2018-03-26T12:32:34.863060 #89666] INFO -- Kitchen: -----> Verifying <default-centos-7>...
	E, [2018-03-26T12:32:35.895347 #89666] ERROR -- Kitchen: ------Exception-------
	E, [2018-03-26T12:32:35.895380 #89666] ERROR -- Kitchen: Class: Kitchen::ActionFailed
	E, [2018-03-26T12:32:35.895405 #89666] ERROR -- Kitchen: Message: 1 actions failed.
	>>>>>> Failed to complete #verify action: [incompatible character encodings: UTF-8 and ASCII-8BIT] on default-centos-7
	E, [2018-03-26T12:32:35.895422 #89666] ERROR -- Kitchen: ----------------------
	E, [2018-03-26T12:32:35.895435 #89666] ERROR -- Kitchen: ------Backtrace-------
	E, [2018-03-26T12:32:35.895448 #89666] ERROR -- Kitchen: /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/test-kitchen-1.20.0/lib/kitchen/command.rb:183:in `report_errors'
	E, [2018-03-26T12:32:35.895461 #89666] ERROR -- Kitchen: /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/test-kitchen-1.20.0/lib/kitchen/

	bundle exec puma --port=9393 config.ru wip [2f7bc9b] (!) modified untracked
	Puma starting in single mode...
	* Version 3.11.3 (ruby 2.5.0-p0), codename: Love Song
	* Min threads: 2, max threads: 10
	* Environment: development
	! Unable to load application: Mustermann::Error: #<Class:0x00007fb6e10c22a0>: Cannot translate Mustermann::AST::Node::WithLookAhead
	Traceback (most recent call last):
	51: from /Users/antho/.rvm/gems/ruby-2.5.0@concierge/bin/ruby_executable_hooks:15:in `<main>'
	50: from /Users/antho/.rvm/gems/ruby-2.5.0@concierge/bin/ruby_executable_hooks:15:in `eval'
	49: from /Users/antho/.rvm/gems/ruby-2.5.0@concierge/bin/puma:23:in `<main>'

	-----> Creating <default-centos-7>...
	Bringing machine 'default' up with 'virtualbox' provider...
	==> default: Importing base box 'bento/centos-7'...
	==> default: Matching MAC address for NAT networking...
	==> default: Checking if box 'bento/centos-7' is up to date...
	==> default: Setting the name of the VM: default-centos-7_default_1519767463185_52919
	==> default: Clearing any previously set network interfaces...
	==> default: Preparing network interfaces based on configuration...
	default: Adapter 1: nat
	==> default: Forwarding ports...

	---
	timestamp: 2018-02-27 01:51:48 UTC
	kitchen_version: 1.19.2
	plugins:
	driver:
	Vagrant:
	class: Kitchen::Driver::Vagrant
	version: 1.2.1
	api_version: 2
	provisioner: