!!! BOSH Lite

!! Resources

* [https://bosh.io/docs/bosh-lite]
* [https://github.com/cloudfoundry/bosh-deployment]

!! Go ahead

{{{
cd ~/workspace
git clone https://github.com/cloudfoundry/bosh-deployment
git clone git@github.com:concourse/concourse.git

git clone ssh://git@www.computerhok.nl:10022/metskem/boshlite.git
cd boshlite/deployments/vbox
rm -vf state.json
# To make sure that VirtualBox has a proper network:
VBoxManage natnetwork remove --netname NatNetwork
VBoxManage natnetwork add --netname NatNetwork --network 10.0.2.0/24 --dhcp on
#
./alldeploy.sh
}}}

This should bring up the bosh director after a while, and also a running concourse bosh deployment at [http://10.244.0.2:8080]

!! ssh access to director

Because we deployed with the operator file jumpbox.yml, we can ssh login to the director.
First get the private key from creds.yml: ''bosh int ./creds.yml --path /jumpbox_ssh/private_key'' and save to a file (~/.ssh id_rsa.vbox), then login with ''ssh -i ~/.ssh/id_rsa.vbox jumpbox@192.168.50.6)''

!! Cleaning up

If you repeat the install of bosh lite a couple of times, that will takes quite some disk space, to clean up, remove the directories {{~/.bosh_virtualbox_cpi/}} and {{~/VirtualBox VM}},the last one will delete all your Virtualbox VMs, beware !!

Also {{~/.bosh}} can take up quite some space (mostly bosh releases)

You might have to also delete the {{~/workspace/boshlite/deployments/vbox/state.json}} if you run into issues with deploying bosh.

Stopping and removing your Vbox VMs:

{{{
VBoxManage controlvm vm-0b17ec48-2d90-42c1-477e-dfbf3fa24973 poweroff
VBoxManage unregistervm vm-0b17ec48-2d90-42c1-477e-dfbf3fa24973 --delete 
}}}