atomic-penguin

gource -1280x800 -a 1 -s 1 -i 10000000000 --max-file-lag 3 --max-files 100000 --hide-filenames --highlight-all-users --disable-bloom --hide-progress --hide-mouse --user-image-dir .git/avatar

atomic-penguin

# Repo name can be a company identifier, like company name.
# Default repo name is corporate
default["yum"]["corp"]["repo_name"] = "corporate"

# Base url should be the URL without RHEL version or architecture.
default["yum"]["corp"]["base_url"]

atomic-penguin

name "base5"
description "Contains run list of roles which are safe to run on all RHEL5 and RHEL6 servers."
override_attributes "inittab" => {
  "runlevel" => "3"
},
"chef_client" => {
  "server_url" => "http://chef.example.com:4000",
  "init_style" => "init"
},
"logwatch" => {

atomic-penguin

Overview

Here is an example shared configuration for knife. You can drop this off in your chef-repo/.chef/ directory, and multiple developers can use the same knife configuration to interact with more than one Chef server, or the Opscode platform.

By using Bash functions and environment variables we can change the chef server, which knife is configured to use, on the fly.

NOTE: knife will probably ignore your ~/.chef/knife.rb once you begin using a shared knife.rb in your chef-repo directory.

Preparation

atomic-penguin

MU Postfix checklist

• Group Aliases (/etc/postfix/aliases)
  • need to notify postalias, postfix reload
  • rebuild-groupaliases.pl
• Valid Recipients (/etc/postfix/local_recipients)
  • need to notify postmap, postfix reload
  • extract_valid_recipients.pl
• Alias mappings (script: rebuild-maps.pl; all postmap, postfix reload)

atomic-penguin

default['esx']['version'] = ""
default['esx']['tarball'] = ""

esx_hw_id = %x[ dmidecode | grep -A4 "BIOS Information" | grep 'Address:' ].split[1]

case esx_hw_id
when "0xEA550"
  set['esx']['version'] = "4.0"
  set['esx']['tarball'] = "VMwareTools-4.0.0-208167.tar.gz"
  set['esx']['checksum'] = "f6f0d2fce35d2abdecf97a522c0b686f709758d37573a4b5dff7a86a17cc485a"

atomic-penguin

rcon.cfg

atomic-penguin

#!/bin/bash
# The purpose of this script is to read an x509 cert, or RSA key, and format it so it can be shoved into a configuration management system.
case "$#" in
  1)
    perl -pe 's!\x0a!\\n!g' $1
  ;;
  *)
    echo "Usage: $0 <filename>"
  ;;
esac

atomic-penguin

#!/bin/sh
yum clean all
mkdir ~/centos; cd ~/centos
wget http://mirror.centos.org/centos/5/os/i386/RPM-GPG-KEY-CentOS-5
wget http://mirror.centos.org/centos/5/os/i386/CentOS/centos-release-5-7.el5.centos.i386.rpm
wget http://mirror.centos.org/centos/5/os/i386/CentOS/centos-release-notes-5.7-0.i386.rpm
wget http://mirror.centos.org/centos/5/os/i386/CentOS/yum-3.2.22-37.el5.centos.noarch.rpm
wget http://mirror.centos.org/centos/5/os/i386/CentOS/yum-updatesd-0.9-2.el5.noarch.rpm
rpm –import RPM-GPG-KEY-CentOS-5
rpm -e –nodeps redhat-release

atomic-penguin

// rcon password
rcon_password "************"
sv_rcon_banpenalty 30
// Number of minutes to ban users who fail rcon authentication
sv_rcon_maxfailures 3
// Max number of times a user can fail rcon authentication before being banned