- Make sure you've pulled down the latest changs in chef-server branch 'mp/postgres-remote-connection-support'. This will be merged into byop-phase-1 shortly.
- copy dev/config.example.yml dev/config.yml
- Edit it so that the following entries are present:
vm:
postgresql:
# Makes the database VM start
start: true
# Configures the chef-server to use the database vm
use-external: true
# Optional if you have cookbook changes to test as part of first reconfigure
omnibus-autoload: [private-chef-cookbooks]
Then vagrant up
.
You can access the database node by using vagrant ssh database
, and sudo postgres
.
By default, the database node will be configured in pg_hba to allow password access to the superuser id (bofh), oc_id, oc_bifrost, oc_erchef originating from the chef-server node.
Other Notes:
- vagrant ssh with no argument will still take you to the chef-server VM
- ./sync will still work asa normal
- You can destroy only the chef-server VM and leave the DB node in place if you want. Use
vagrant destroy chef-server
instead ofvagrant destroy