nicwaller

'''Build script interaction with TeamCity using Service Messages
​
https://confluence.jetbrains.com/display/TCD9/Build+Script+Interaction+with+TeamCity
'''
​
import time
import re
import os
from contextlib import contextmanager
​

nicwaller

#!/bin/bash

# ------BEGIN LOGSTASH------

application_tag="bash"

if [ -z "$LOGFILE" ]; then
  [ -d ~/log ] || mkdir ~/log
  export LOGFILE=~/log/${application_tag}-logstash.log
fi

nicwaller

#!/bin/bash

# Install Graphite
mkdir graphite && cd graphite
virtualenv venv
venv/bin/pip install Django==1.8 django-tagging
# You might need to do this instead: venv/bin/pip install --user Django==1.8
venv/bin/pip install carbon whisper graphite-web Twisted==15.2

# Configure Graphite

nicwaller

#!/bin/bash
vagrant box add bento/ubuntu-14.04
vagrant init bento/ubuntu-14.04
vagrant up --no-provision
vagrant ssh
# Enter shell inside vagrant box
wget -O - https://omnitruck.chef.io/install.sh | sudo bash -s -- -v 12.14.89
rm /tmp/chef*{rpm,deb}
exit
# Exit shell inside vagrant box

nicwaller

Slack
Dropbox
DocuSign
Stripe
Cloudera
SurveyMonkey
MailChimp
Squarespace
AppDynamics
Adyen

nicwaller

#!/bin/bash

# Example output:
# ~$ ./slowlog_all.sh
# 1779.2 ms /etc/redis/reports.conf
# 65.934 ms /etc/redis/actions.conf

for file in $(ls -1 /etc/redis/*.conf); do
  name=$(basename $file);
  port=$(awk '/^port/ {print $2}' $file);

nicwaller

% vagrant box add ubuntu/trusty64
% vagrant box update
% vagrant init ubuntu/trusty64
% vagrant up --no-provision
% vagrant ssh
vagrant$ wget -O - https://omnitruck.chef.io/install.sh | sudo bash
vagrant$ rm /tmp/chef*{rpm,deb}
vagrant$ exit
% vagrant package --output nicwaller-trusty64-chef12.box
% vagrant box add nicwaller/trusty64-chef12 nicwaller-trusty64-chef12.box

nicwaller

Keybase proof

I hereby claim:

• I am nicwaller on github.
• I am nicwaller (https://keybase.io/nicwaller) on keybase.
• I have a public key whose fingerprint is C052 64EF DDBA 7728 5A4E A89F 3686 0D5E 0CD7 E579

To claim this, I am signing this object:

nicwaller

Environment workflow

Problem

The status quo today is that we do not use dependency constraints on our internal cookbooks. This inhibits our ability to make changes because all changes must be backward-compatible. And even when our changes are backward-compatible, sometimes we promote cookbooks in the wrong order and end up with a failure.

Solution

We need to use two kinds of constraint.

nicwaller

---

# The key ideas of integration tools is that the entire routing solution should be implemented
# between the input/output borders. This provides some nice properties: for any input, you can
# determine where it will go. For any output, you can trace back all the possible inputs.
# If you have a service that will only send to exactly one email address (eg. AWS) then you
# can set up fan-out rules. If you are deprecating a service (eg. Slack) then you can identify
# and redirect all emails that have Slack as a destination. Unlike a forwarding rule on an
# Exchange account, you end up with version history. And unlike an Exchange forwarding rule,
# you always know where the email is coming from, so you can shut it down at its source.