Would love to get people together to speak with those actively using chef and puppet to figure out how we can lower the bar for development of drupal sites using a continuous delivery model.

My personal interest lies in creating a tool that includes instructions that can be used to spin up a local example (to quickly show people the benefits), and a basic cloud infrastructure. Together these would be used to build sites as installation profiles using mainline git development, building a canonical "binary" deb package in the first step, and deploying that to all subsequent testing/QA/stage/prod environments in later stages of the pipeline (see slideshare link below for explanation of continuous delivery)

My tools of choice for automating the configuration of this setup would be chef for general config management, vagrant for booting the local example in a VM, and spiceweasel for deploying this tool into the cloud. I'm particularly interested in helping the Pennyworth project (an in-progress continuous delivery pipeline setup) to accomodate the building of Drupal sites.

Pennyworth itself sets up jenkins to coordinate the build pipeline, fpm for creating simple deb package artifacts in the first stage of the pipeline, and reprepro to storing these artifacts in a apt-repo (would like to drop in freight, a better tool for apt-repos). Native package managers and automatically versioned debs are used for deployment in this case, but drush-archive tarballs and capistrano might also be an option.

http://www.slideshare.net/jezhumble/continuous-delivery-5359386

http://wiki.opscode.com/display/chef/Home
http://vagrantup.com/
http://wiki.opscode.com/display/chef/Spiceweasel
https://github.com/myplanetdigital/pennyworth-drupal
http://jenkins-ci.org/
https://github.com/jordansissel/fpm
http://mirrorer.alioth.debian.org/
http://rcrowley.org/articles/packaging.html