- You are using
GCP
orAWS
-bbl
only supports these bbl
is installed- You have set the required environment variables for your IaaS environment as documented in
bbl up --help
and also the README of bosh-bootloader - You have both
cf-deployment
andbosh-deployment
repos handy
bbl
only accepts a single ops file, so you need to concatenate all the necessary ops files into a single file, and then pass that to the bbl up
command. The ops files you will need reside in the bosh-deployment repository.
For AWS
, you will need:
- bosh-lite.yml
- bosh-lite-runc.yml
- jumpbox-user.yml
For GCP
, you will need the above and also:
- gcp/bosh-lite-vm-type.yml
The command you'll need to run will look something like:
bbl \
up \
--name <ENV_NAME> \
--ops-file <CONCATENATED_OPS_FILE>
# ...
# IaaS-specific flags
# ...
Until bbl
offers a --lite
option, you'll also need to ensure the ports 80,443,2222
are opened on the firewall to the vm created by bbl
.
There a several ways to target a bosh director.
This doc will use alias-env
and -e
,
but you can set environment variables if you prefer.
First, create an alias for your director:
bosh -e $(bbl director-address) --ca-cert <(bbl director-ca-cert) alias-env MY_ENV
Then, log in:
bosh -e MY_ENV login
# Enter the output of `bbl director-username` and `bbl director-password`
bosh \
-e MY_ENV
update-cloud-config \
cf-deployment/bosh-lite/cloud-config.yml
bosh \
-e MY_ENV \
upload-stemcell \
https://bosh.io/d/stemcells/bosh-warden-boshlite-ubuntu-trusty-go_agent
bosh \
-e MY_ENV
-d cf \
deploy \
cf-deployment/cf-deployment.yml \
-o cf-deployment/operations/bosh-lite.yml \
--vars-store vars-store.yml \
-v system_domain=<SYSTEM_DOMAIN>