Added Chris Snell's cookbook and a Vagrantfile that creates PostgreSQL servers.

Incorporated a cookbook that Chris created that creates a database user and table space.

Bundled this cookbook with the overall create a PostgreSQL node, and saved into the
Vagrant_single_db_works_out_of_box Vagrantfile. When this VM is launched you should
be able to access it. I modified my Barbican API's barbican-api.conf file to add this
configuration:

sql_connection = postgresql+psycopg2://barbican:<barbican password here>@localhost:5437/barbican_api

Note the non-standard port of 5437, to avoid conflicting with my local PostgreSQL install.
Add Vagrant file to standup a second Postgres node (the slave node).

Both database's stand up, but more is needed to complete the configuration.
For example, this site looks interesting for configuring replication:
http://bartek.im/blog/2012/12/04/postgresql-92-streaming-primer.html
Add cloudpassage to base role
Add New Relic and CloudPassage recipes

There is a new role called "api" used for barbican-api that sets
up New Relic application monitoring. New Relic server monitoring
and CloudPassage have been added to the base role.
Make cloudpassage pick up the provided key
Add starting master/slave configs, very raw.
Merge pull request #3 from greyshi/master

Add CloudPassage and New Relic chef recipes
Merge/resolve Berksfile conflict.
Added queue, worker and base cookbooks; Revamped Vagrant file and using different internal IPs, so API and db can connect now.
Removing unneeded Vagrant files
Fixed dependency issues; Version bumped to avoid colliding with Chef Server recipes; Ignor Users folder generated by knife;
Cleaned up the Vagrantfile to just create the 4 basic nodes; Created temp file to hold master/slave db stuff under developme
Restore VM base box to the standard opscode one.
Comment out newrelic recipe for now
Merge pull request #4 from jfwood/master

Add starting master/slave configs, very raw.