Add cookbook to spin up a Barbican network (starting with the API node)

We eventually want the main Vagrantfile to spin up a standalone Barbican
network, complete with API, worker and database nodes. This commit just
stands up a Barbican API node in standalone mode.
Added port forwarding and fixed Chef barbican api recipe

The generated Barbican API node was functional, but could not be reached from outside
until the port forwarding (for 9311 and 9312) was added.

The Chef api recipe was also not idempotent regarding the Fedora EPEL installation step,
so that was fixed to first check to see if that rpm was already installed on the node.
Add cookbook and Vagrant file to bring PostgeSQL databases to life.

We need to run Barbican with PostgreSQL in a master/slave clustered mode.
The files in this commit are initial files into that effort. This feature
is not working as of yet though.
Add files for manual PostgreSQL master/slave configuration.

The repmgr cookbook was crashing with Vagrant on both CentOS (looking for
unavailable packages or crashing due to uninitilized Chef variables) and on
Ubunto Raring (just hangs). Since PostgreSQL 9.2 supports replication, this
set of files attempts to utilize those built in features instead of using
repmgr.
Fixing broken barbican-api recipe
Merge pull request #2 from jfwood/master

   Add cookbook to spin up a Barbican network (starting with the API node)