Mark Bainter mbainter

The files in this gist are for having Jenkins automatically manage a chef repository using git submodules. This allows for clean, clutter free management of individual cookbooks, and individual respositories for roles, environments and data bags in our chef-repo.

The process relies on using Github (we use Github Enterprise) and Jenkins in combination with the Jenkins Github plugin to notify Jenkins when a repository has changed.

Our chef-repo directory looks something like:

chef-repo
    - cookbooks
          - Each cookbook is a git submodule managed by Jenkins
    - data_bags (git submodule managed by Jenkins)

Graphing Widget

The graphing widget shows graphs using the Rickshaw graphing library. The names of data fields should be (vaguely) familiar if you've used Rickshaw before.

It's recommended that you replace the /assets/javascripts/rickshaw.min.js from your dashboard with the latest from here.

Supported HTML data fields

So, you made a change to your dashboard, and now you have to run all over the building, plugging in a keyboard, and reloading the dashboard on the various TVs in your office. What if you could reload all the dashboard from the comfort of your desk?

Add this widget to the very bottom of your dashboard, after the "gridster" div:

<div class="gridster">
  <ul>
    <li data-row="1" data-col="1" data-sizex="1" data-sizey="1">
      <div data-view="Image" data-image="/benbria/loop.png" style="background-color:#666766"></div>
    </li>

#A script to post back to Slack via the webhooks API

##why this exists?

Slack's own hubot adapter needs the hubot installation to be accessible via web. This can be problematic in some cases, as a security risk.

This hack let's you run your Hubot behind a firewall, and connect to Slack via the IRC gateway.

To respond, Hubot uses the incoming webhooks end-point of Slack.

	! --------------------------------------------------------------------------------
	! This example configuration shows what WE did to get Amazon VPC working with our
	! ASAs. We use version 8.3(1). This config has not been reviewed or otherwise
	! blessed in any way by anyone at Amazon. YMMV.
	!
	! It differs from Amazon's supplied config by using two different sets of
	! crypto maps and ACLs, so it brings both tunnels up simultaneously.
	!
	! For the purposes of the example, the physical datacenter network is 172.16.1.0/24
	! and the VPC is 10.0.0.0/16.

	# Description:
	# This script receives pages in the formats
	# /usr/bin/curl -d host="$HOSTALIAS$" -d output="$SERVICEOUTPUT$" -d description="$SERVICEDESC$" -d type=service -d notificationtype="$NOTIFICATIONTYPE$ -d state="$SERVICESTATE$" $CONTACTADDRESS1$
	# /usr/bin/curl -d host="$HOSTNAME$" -d output="$HOSTOUTPUT$" -d type=host -d notificationtype="$NOTIFICATIONTYPE$" -d state="$HOSTSTATE$" $CONTACTADDRESS1$
	#
	# Based on a gist by oremj (https://gist.github.com/oremj/3702073)
	#
	# Configuration:
	# HUBOT_NAGIOS_URL - https://<user>:<password>@nagios.example.com/cgi-bin/nagios3
	#

	# -- mode: ruby --
	# vi: set ft=ruby :

	# This configuration requires Vagrant 1.5 or newer and two plugins:
	#
	# vagrant plugin install vagrant-hosts ~> 2.1.4
	# vagrant plugin install vagrant-auto_network ~> 1.0.0
	#
	# After installation, the following steps will spin up a master and agent that
	# can communicate with each other:

	wget http://stedolan.github.io/jq/download/linux64/jq
	aws ec2 describe-instances --filters "Name=tag:Name,Values=$NAME" \
	"Name=instance-state-name,Values=running" \
	\| jq -r \
	".Reservations[] \| .Instances[] \| .InstanceId" \

	aws ec2 describe-volumes --filters \
	"Name=status,Values=available" \
	\| jq -r ".Volumes[] \| .VolumeId" \

	if exists("g:loaded_syntastic_clint_checker")
	finish
	endif

	let g:loaded_syntastic_clint_checker = 1
	let s:save_cpo = &cpo
	set cpo&vim

	function! SyntaxCheckers_c_clint_GetLocList() dict
	let makeprg = self.makeprgBuild({

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048