sjourdan

namespace :ec2 do
  # setup chef config
  # assumes this file is sibling to .chef dir, ex: CHEF_REPO/tasks
  config = File.join(File.dirname(__FILE__), '..', '.chef', 'knife.rb')
  Chef::Config.from_file(config)

  require 'active_support'
  require 'aws'

  desc 'Delete any ec2-based chef nodes that no longer exist'

sjourdan

git reset --soft HEAD~1

sjourdan

search(:node, "chef_environment:dev") do |matching_node|
  puts matching_node.to_s
end

sjourdan

#!/bin/bash

PATHPATCH="/root/patch-ovh"
PATHRCS="/etc/default"
PATHCHECK="/etc/init.d"
PATHINITTAB="/etc"
ECHO="/bin/echo"
APTGET="/usr/bin/apt-get"
WGET="/usr/bin/wget"
RM="/bin/rm"

sjourdan

Keybase proof

I hereby claim:

• I am sjourdan on github.
• I am sjourdan (https://keybase.io/sjourdan) on keybase.
• I have a public key whose fingerprint is 31D1 CFDB DF8F 1B53 82A1 2FCF 204B F835 CEFF 35EF

To claim this, I am signing this object:

sjourdan

The Operations Report Card

Source: http://www.opsreportcard.com/.

Public Facing Practices

1. Are user requests tracked via a ticket system?
2. Are "the 3 empowering policies" defined and published?
3. Does the team record monthly metrics?

sjourdan

<% if @port != 80 -%>
	Listen <%= @port %>
<% end -%>
 
<VirtualHost *:<%= @port %>>
  ServerAdmin webmaster@localhost
 
  DocumentRoot <%= @document_root %>
  <Directory />
    Options FollowSymLinks

sjourdan

#cloud-config

users:
  - name: demo
    sudo: ['ALL=(ALL) NOPASSWD:ALL']
    groups: sudo
    shell: /bin/bash

chef:
  install_type: "omnibus"

sjourdan

April 2015 Links

• Project Atomic Quick Start
• Kubernetes Getting Started w/Vagrant
• Kubernetes Getting Started
• Kubernetes Getting Started on Fedora
• Configuring Kubernetes via Ansible
• Kartar's Docker Book Code
• Terraform in Atlas
• Terraform Providers

sjourdan

Creating a Cloud Abacus Easy

This is going to be another scripting challenge.... you may use any language tools you want to solve it.

The task is to create two scripts (or one script with a symlink, whatevs) that will take as its only argument a 4 bit integer value (0-15) and create a file with a path based on the bit pattern. The directories should be created with the most significant bit first and will be named either "0" or "1" depending on the value of the bit in that position.

The first script should be called /usr/local/bin/seta and will use /var/math/a as its root directory. The second script will be /usr/local/bin/setb and use /var/math/b for its root. So, calling /usr/local/bin/seta 10 should create the directory /var/math/a/1/0/1/0/. Any files in the subdirectories will be ignored.

Your script should clear its target directory (/var/math/[a|b]) before writing files to ensure that data from previous runs will be removed. A third script called /usr/local/bin/adder has been provided and will add