Ryan Dooley 3rdman

A Brief Introduction to Fabric

Fabric is a deployment management framework written in Python which makes remotely managing multiple servers incredibly easy. If you've ever had to issue a change to a group servers, this should look pretty familiar:

for s in $(cat servers.txt); do ssh $s service httpd graceful; done

Fabric improves on this process by providing a suite of functions to run commands on the servers, as well as a number of other features which just aren't possible in a simple for loop. While a working knowledge of Python is helpful when using Fabric, it certainly isn't necessary. This tutorial will cover the steps necessary to get started with the framework and introduce how it can be used to improve on administering groups of servers.

Backend Architectures

ARCHITECTURES

Twitter

ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats

One of my favorite past times is to look at the notebooks of famous scientists. Da Vinci's notebook is well known, but there plenty others. Worshipping Da Vinci like no other, I bought a Think/Create/Record journal, used it mostly to keep jot down random thoughts and take notes. This was great in the beginning, but the conformity of lines drove me nuts. Only moleskines made blank notebooks, so I had to buy one.

At the same time I started a freelance project. The project itself is irrelevant, but suffice to say it was very complex and spanned several months. It seemed like a perfect opportunity to use the moleskine. Looking back, all my entries fell under few categories:

Todo
Question
Thought
Bug
Feature

	#!/bin/bash
	#
	# script formats bonnie output and calls gnuplot to create a png graph
	# of various bonnie parameters.
	#
	# feed script bonnie++ output - it will attempt to find the last line of bonnie output
	# which is all it really cares about anyway
	#
	# eg: Using uid:65534, gid:65534.
	# Writing a byte at a time...done

	---
	# ^^^ YAML documents must begin with the document separator "---"
	#
	#### Example docblock, I like to put a descriptive comment at the top of my
	#### playbooks.
	#
	# Overview: Playbook to bootstrap a new host for configuration management.
	# Applies to: production
	# Description:
	# Ensures that a host is configured for management with Ansible.

	DoS / slow DoS:

	https://www.owasp.org/images/4/43/Layer_7_DDOS.pdf
	http://docs.cpanel.net/twiki/bin/view/EasyApache/Apache/SlowlorisAttacks
	http://en.nsfocus.com/SecurityReport/2013%20NSFOCUS%20Mid-Year%20DDoS%20Threat%20Report.pdf
	http://blog.spiderlabs.com/2011/07/advanced-topic-of-the-week-mitigating-slow-http-dos-attacks.html
	http://sourceforge.net/projects/pyloris/
	http://security.stackexchange.com/questions/19698/mitigating-anonymous-dos-tor-combined-with-pyloris
	https://blogs.akamai.com/2013/09/slow-dos-on-the-rise.html
	https://community.qualys.com/blogs/securitylabs/2011/09/19/testing-web-servers-for-slow-http-attacks

	#!/usr/bin/env ruby

	require 'rubygems'
	require 'pry'
	require 'socket'
	$:.unshift '/home/jof/src/net-netconf/lib'
	$:.unshift '/home/jof/src/net-ssh/lib'

	require 'net/netconf'
	require 'net/ssh'

	# see http://stackoverflow.com/questions/5880962/how-to-destroy-jobs-enqueued-by-resque-workers - old version
	# see https://github.com/defunkt/resque/issues/49
	# see http://redis.io/commands - new commands

	namespace :resque do
	desc "Clear pending tasks"
	task :clear => :environment do
	queues = Resque.queues
	queues.each do \|queue_name\|
	puts "Clearing #{queue_name}..."

	AUDIT type=%{WORD:audit_type} msg=audit\(%{NUMBER:audit_epoch}:%{NUMBER:audit_counter}\): user pid=%{NUMBER:audit_pid} uid=%{NUMBER:audit_uid} auid=%{NUMBER:audit_audid} subj=%{WORD:audit_subject} msg=%{GREEDYDATA:audit_message}
	AUDITLOGIN type=%{WORD:audit_type} msg=audit\(%{NUMBER:audit_epoch}:%{NUMBER:audit_counter}\): login pid=%{NUMBER:audit_pid} uid=%{NUMBER:audit_uid} old auid=%{NUMBER:old_auid} new auid=%{NUMBER:new_auid} old ses=%{NUMBER:old_ses} new ses=%{NUMBER:new_ses}

	server {
	# Redirect yoursite.com to www.yoursite.com
	server_name yoursite.com;
	rewrite ^(.*) http://www.yoursite.com$1 permanent;
	}

	server {

	# Tell nginx to handle requests for the www.yoursite.com domain
	server_name www.yoursite.com;