[tom_usher]

This looks great, nice work.

For the dev/prod parity use case, where do you usually draw the line between Packer and Vagrant? I'm currently building boxes with Veewee with all dependencies pre-installed and distributing this to the team. Vagrant could easily deal with this, installing dependencies when the VM is launched using provisioners.

Does anyone have any preferences/reasons to go one way or another?

[mitchellh]

It depends on what works best for you. In big organizations, I prefer to take the Veewee approach (although in this case replacing Veewee with Packer). If you use Veewee, see: http://www.packer.io/docs/templates/veewee-to-packer.html