- IRC:
#bosh
on freenode - Google groups: bosh-users & bosh-dev & vcap-dev (for CF)
A local development environment for BOSH using Warden containers in a Vagrant box.
This readme walks through deploying Cloud Foundry with BOSH Lite. BOSH and BOSH Lite can be used to deploy just about anything once you've got the hang of it.
-
Install latest version of
bosh_cli
.gem install bosh_cli
Refer to BOSH CLI installation instructions for more information and troubleshooting tips.
-
Install Vagrant.
Known working version:
$ vagrant --version Vagrant 1.6.3
-
Clone this repository.
Installation instructions for different Vagrant providers:
- Virtualbox (below)
- VMware Fusion
- AWS
-
Install Virtualbox
Known working version:
$ VBoxManage --version 4.3.14r95030
-
Start Vagrant from the base directory of this repository, which contains the Vagrantfile. The most recent version of the BOSH Lite boxes will be downloaded by default from the Vagrant Cloud when you run
vagrant up
. If you have already downloaded an older version you will be warned that your version is out of date. You can use the latest version by runningvagrant box update
.vagrant up --provider=virtualbox
-
Target the BOSH Director and login with admin/admin.
# if behind a proxy, exclude this IP by setting no_proxy (xip.io is introduced later) $ export no_proxy=192.168.50.4,xip.io $ bosh target 192.168.50.4 lite Target set to `Bosh Lite Director' $ bosh login Your username: admin Enter password: ***** Logged in as `admin'
-
Add a set of route entries to your local route table to enable direct Warden container access every time your networking gets reset (e.g. reboot or connect to a different network). Your sudo password may be required.
bin/add-route
The local VMs (virtualbox, vmware providers) will be accessible at 192.168.50.4
. To change this IP, uncomment the private_network
line in the appropriate provider and change the IP address.
config.vm.provider :virtualbox do |v, override|
# To use a different IP address for the bosh-lite director, uncomment this line:
# override.vm.network :private_network, ip: '192.168.59.4', id: :local
end
- bosh cck documentation for restoring deployments after VM reboot
- bosh ssh documentation for SSH into deployment jobs
- Offline documentation to configure BOSH lite firewall rules
- Starting over again is often the quickest path to success; you can use
vagrant destroy
from the base directory of this project to remove the VM.
We publish pre-built Vagrant boxes on Amazon S3. It is recommended to use the latest boxes. To do so get a latest copy of the Vagrantfile from this repo and run vagrant up
.