W6D3 ME UB

I was concerned about my bench since I haven’t done straight bench in a number of months. I’ve done a lot more triceps work and close benching, but not much direct chest work. I felt like I could hit my last max of 315, but I held back out of concern. Instead of focusing as much on the total weight, I focused on form and efficiency. Writing this up the day after, I’m surprised I have no second-day soreness. My right trapezius has been sore for several weeks, but it didn’t seem to affect my bench effort too much.

bench: 135×5, 165×5, 195×5, 225×3, 255×2, 275×1, 295×1, 225×5 (two sets)
rope pressdown: 10×6, 12×6, 14×6 (four sets)
barbell row: 135×6, 185×5 (three sets)
face pull: 8×8, 9×8, 10×8

October 10, 2009 | Filed Under lifting | Leave a Comment 

Installing Passenger with Puppet

Alongside our slow but steady move towards using Puppet for configuration management, our rails team has made the transition to Passenger (‘bye-bye mongrels’). Passenger has a fine installation mechanism for installation, but we wanted to be able to push out production-level machines and VMs with the most minimal level of manual intervention.

I found a decent bash script here that we modified to play well with puppet.


#!/bin/bash
#
# passenger_config.sh
export PASSENGER="2.2.5"
export MODDIR=/usr/lib/ruby/gems/1.8/gems/passenger-$PASSENGER/ext/apache2
export LOADER=/etc/httpd/mods-available/passenger.load

yes '' | /usr/bin/passenger-install-apache2-module

if [ -f $MODDIR/mod_passenger.so ] ; then
echo "LoadModule passenger_module $MODDIR/mod_passenger.so" > $LOADER
echo "PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-$PASSENGER" >> $LOADER
echo "PassengerRuby /usr/bin/ruby" >> $LOADER
ln -s $LOADER /etc/httpd/mods-enabled

else
echo I didn\'t create /etc/httpd/mods-available/passenger.load because there is no $MODDIR/mod_passenger.so.
fi

/etc/init.d/httpd configtest && /etc/init.d/httpd graceful

So our passenger_install class runs the above bash script and subscribes to a file named reconfig_passenger. This allows us to upgrade our passenger install by only touching the reconfig_passenger file on the puppetmaster. The puppet client detects there has been a modification to the file and re-runs the passenger_config script.

# class for installing passenger
class passenger_install {
file { "/usr/bin/passenger_config.sh":
source => "puppet://puppetmaster/files/passenger_config.sh",
owner => "root",
group => "root",
mode => "775"
}

package { "passenger":
ensure => "2.2.5",
provider => "gem"
}
file { "/etc/reconfig_passenger":
source => "puppet://puppetmaster/files/reconfig_passenger",
owner => "root",
group => "root",
mode => "664"
}
# only run config script if this file changes
exec { "/usr/bin/passenger_config.sh":
subscribe => file[ "/etc/reconfig_passenger" ],
refreshonly => true
}
}

We can now roll out production-level VMs in about 22 minutes with a combination of kickstart and puppet. There are a few manual issues existing that are due to our home-rolled python packages, but I’m rather happy with what we’ve been able to do. Even better, we start to get a layer of control over packages, permissions and all innumerable tasks that were done to bring a machine up to match our production stack.

October 10, 2009 | Filed Under geek | 2 Comments