milesbxf

###################################################
##
## Alertmanager YAML configuration for routing.
##
## Will route alerts with a code_owner label to the slack-code-owners receiver 
## configured above, but will continue processing them to send to both a
## central Slack channel (slack-monitoring) and PagerDuty receivers
## (pd-warning and pd-critical)
##

jfryman

#!/usr/bin/env bash
#
# HAProxy wrapper to make reloads safer
#
# THIS FILE IS AUTOMATICALLY DISTRIBUTED BY PUPPET. ANY LOCAL CHANGES WILL BE OVERWRITTEN!

HAPROXY_DIR=/etc/haproxy
HAPROXY_BIN=/usr/sbin/haproxy

check() {

fnichol

Auto-enable Local HTTP Caching in Test Kitchen

Note: total experiment and hack, looks nasty, could be awesome:

Setup

• Drop the kitchen.local.yml into $HOME/.kitchen/config.yml
• Install polipo (with Mac: brew install polipo, with Ubuntu: apt-get install polipo)
• Drop polipo-start and polipo-console somewhere useful (perhaps $HOME/bin?)

jbenet

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

atmos

@holman got a request about our deployment system, heaven

I know it's not a high priority, but has there been any activity on open-sourcing the core Heaven gem?

There is. I've been working on extracting the non-GitHub specific parts into two gems. This first is a CLI portion called hades. The second is an HTTP API portion called heaven.

When you open source something previously used as in internal tool like Heaven, Hubot, Boxen, etc., how do you manage and hook in the parts that need to stay internal?

Normally I focus around four questions:

timf

• Forecasting for Cloud computing on-demand resources based on pattern matching
• Auto-scaling Techniques for Elastic Applications in Cloud Environments
• Auto-Scaling Model for Cloud Computing System
• Rebalancing in a Multi-Cloud Environment
• Infrastructure Outsourcing in Multi-Cloud Environment
• Workload Classification for Efficient Auto-Scaling of Cloud Resources
• Dynamically Scaling Applications in the Cloud
• [Optimal Autoscaling in the IaaS Cloud](http://www.cse.yorku.ca/~hamoun/p

millisami

This is a little trick I use to spin up the packages instalation on Debian/Ubuntu boxes in Vagrant.

I add a simple function that checks if a directory named something similar to ~/.vagrant.d/cache/apt/opscode-ubuntu-12.04/partial (it may have another path in Windows or MacOS) and create the directory if it doesn't already exist.

def local_cache(box_name)
  cache_dir = File.join(File.expand_path(Vagrant::Environment::DEFAULT_HOME),
                        'cache',
                        'apt',
                        box_name)

juanje

This is a little trick I use to spin up the packages instalation on Debian/Ubuntu boxes in Vagrant.

I add a simple function that checks if a directory named something similar to ~/.vagrant.d/cache/apt/opscode-ubuntu-12.04/partial (it may have another path in Windows or MacOS) and create the directory if it doesn't already exist.

def local_cache(basebox_name)
  cache_dir = Vagrant::Environment.new.home_path.join('cache', 'apt', basebox_name)
  partial_dir = cache_dir.join('partial')
  partial_dir.mkdir unless partial_dir.exist?
 cache_dir

bhenerey

In a perfect world, where things are done well, not just quickly, I would expect to find the following when joining the company:

Documentation

• Accurate / up-to-date systems architecture diagram

• Accurate / up-to-date network diagram

• Out-of-hours support plan

• Incident management plan

ryandotsmith

The Worker Pattern

Contents

• Introduction
• Definition
• Examples
• Links

Introduction