Puppet Solo (AKA: supply_drop)

Similar to knife-solo for use with chef, supply_drop allows you to provision servers using puppet without the need for a puppet master server. It uses capistrano for executing commands on the remote server. I put together a working sample set of puppet and supply_drop deployment scripts for provisioning a postgres server.

See the github repo at  https://github.com/house9/puppet-solo-hello-world

Resources

• http://www.confreaks.com/videos/2479-railsconf2013-devops-for-the-rubyist-soul
• https://speakerdeck.com/jtdowney/devops-for-the-rubyist-soul-at-rubynation-2013

WAL-e chef cookbook

Postgres has various backup and restore options

• http://www.postgresql.org/docs/9.2/static/backup.html

Do you have a recovery plan in case your Postgres server crashes - your daily pg_dump is probably not going to cut it.

Postgres uses Write-Ahead Logging (WAL)

Write-Ahead Logging (WAL) is a standard method for ensuring data integrity. A detailed description can be found in most (if not all) books about transaction processing. Briefly, WAL's central concept is that changes to data files (where tables and indexes reside) must be written only after those changes have been logged, that is, after log records describing the changes have been flushed to permanent storage. If we follow this procedure, we do not need to flush data pages to disk on every transaction commit, because we know that in the event of a crash we will be able to recover the database using the log: any changes that have not been applied to the data pages can be redone from the log records. (This is roll-forward recovery, also known as REDO.)

• from http://www.postgresql.org/docs/9.2/static/wal-intro.html

Setting up Continuous Archiving and Point-in-Time Recovery (PITR) for your Postgres WAL files is very complex, lucky for us the WAL-e project has simplified this process greatly. WAL-e has utilities for sending all WAL files to an AWS S3 bucket as the log files are being generated. More Information, see:

• http://www.postgresql.org/docs/9.2/static/continuous-archiving.html

• https://github.com/wal-e/wal-e

Recently I put together a chef cookbook which installs WAL-e on a Postgres instance, see:

• https://github.com/house9/wal-e-cookbook

• https://github.com/house9/use_wal_e

Vagrant and puppet postgres 9.2 on ubuntu

Some vagrant configuration to install postgres 9.2 using puppet



Resources

• https://forge.puppetlabs.com/puppetlabs/postgresql
• https://github.com/puppetlabs/puppetlabs-postgresql

Vagrantfile for setting up multiple machines with chef configuration

Example Vagrantfile below for setting up multiple virtual machines and using chef to provision them



Resources

• http://docs.vagrantup.com/v2/multi-machine/index.html 
• http://jbbarth.com/posts/2011-03-20-vagrant-provisioning-with-chefsolo.html 

HipChat is now free!

Just got an email from HipChat - now free for small groups - awesome!

> random tricks you can do with Rails

There are bunch of really good nuggets in this presentation:

• http://www.confreaks.com/videos/889-railsconf2012-ten-things-you-didn-t-know-rails-could-do 
• https://speakerdeck.com/jeg2/10-things-you-didnt-know-rails-could-do

Ruby on Rails continuous integration (CI) with Jenkins the easy way with Chef and Knife

Do you need a CI build setup for your Ruby on Rails app?

Here are some chef / knife solo scripts that will deploy a Jenkins server to run your CI build - you could be up and running in less than 1/2 an hour

https://github.com/house9/ci_chef_jenkins_rails

Check out the README for details